Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hello community, just a straightforward question: by connecting a report to Dataverse as its source, can the data in my published report auto refresh when the browser window refreshes?
If not, what would be the easiest method to achieve this when Dataverse is used?
Thank you!
Solved! Go to Solution.
Refreshing the browser window doesn't refresh the underlying dataset in Import mode, just the visuals. You can use DirectQuery with Dataverse, in which case you can get the visuals to auto refresh periodically (meaning there's no need to manually refresh the browser) but bear in mind that DirectQuery can be slow.
Here's the relevant documentation:
https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-automatic-page-refresh
Refreshing the browser window doesn't refresh the underlying dataset in Import mode, just the visuals. You can use DirectQuery with Dataverse, in which case you can get the visuals to auto refresh periodically (meaning there's no need to manually refresh the browser) but bear in mind that DirectQuery can be slow.
Here's the relevant documentation:
https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-automatic-page-refresh
Thank you very much! Now that I tried this out with my first directquery connection ever (have only been a developer for almost four years), I just have a straight DQ question: whereas I used to write my DAX columns and measures in the desktop (cached/import connection), am I now supposed to write all DAX into Dataverse calculated fields??
Many thanks for clearly answering my question up front. Double kudos if you can answer this follow-up.
To the extent the logic in your DAX columns is easy to replicate in Dataverse, I'd favor leveraging the latter as it might perform better. The larger the dataset the more it's recommended to avoid DAX calculated columns and move the necessary transformations upstream (Dataverse in your case).
That said I can't vouch for Dataverse performance with calculated fields, I've only used Dataverse cursorily. With a "regular" SQL server I'd go with creating the columns in SQL views for sure.
Awesome, I really appreciate the sanity check here. Good thing I'm studying for the PL-200 exam and should be able to figure out those calculated fields -- as mentioned I've never put my hands on DV or DQ until very recently.
Thanks again.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
30 | |
28 | |
23 | |
21 | |
18 |
User | Count |
---|---|
56 | |
37 | |
28 | |
24 | |
21 |