Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
I have a dataset that I changes regularly thoughout the day. I originally created a report using Import data and set the frequency every 30 minutes, which in this case is not ideal but adequate. I started to get regular refresh errors based on capacity which in turn shut my refresh off after 4 failures. So I converted the query to Direct Query instead of Import thinking that this would solve my refresh problem. I completed the report last Friday. Well I checked the report today, and it looks like it has not refreshed since last Friday when the report is deployed. It works fine in Desktop.
I checked the Semantic model and it shows 2 options for refresh. Daily or Weekly. Neither will work for the report. I was under the impression that for frequenly changing data not to use Import but use Direct which I did. How can I get this to work? Very frustrating
Hello @bdherh,
We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
Hi @bdherh,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @FBergamaschi & @Natarajan_M for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
Hi @bdherh ,
I understand your scenario correctly: you changed the import mode to direct query mode, but you're not seeing the latest data in the report. Could you please provide details on the following questions?
Thanks
If this response was helpful in any way, I’d gladly accept a kudo.
Please mark it as the correct solution. It helps other community members find their way faster
Hi @bdherh
whether you use Import or DirectQuery, it seems your capacity is not enough for the data size
Either you shrink the data size (eliminating useless columns for example ar aggregating the data) or you increase the capacity. I do not see other options.
Desktop uses the memory of the machine you use it run, in cloud you use the resources corrsponding to your capacity
If this helped, please consider giving kudos and mark as a solution
@me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
I put a manual refresh button on the reports to give the users the ability to refresh the data if it has not already been reset. Not sure why I had to do this if it is a Direct data access, but I did and it is working for them
hello @bdherh
if pbi desktop and manual refresh button worked then it might not direct query row limit issue.
what error does it show in refresh report?
some sources need a connection or gateway to make schedule refresh works.
Thank you.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 53 | |
| 39 | |
| 35 | |
| 19 | |
| 18 |
| User | Count |
|---|---|
| 73 | |
| 72 | |
| 38 | |
| 35 | |
| 26 |