Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
When a report based on an import model is published to the service, with new look on, it displays the last refresh time in the header, top-centre of the report page, along side the Title and Contacts.
Changing this to be a composite model with Direct Query (DQ) connection(s) appears to make this last refresh time disappear from the report page header.
I assume as some of the data in the report is queried when a user interacts, and some is on a scheduled refresh import, the last refresh time is not displayed as it would not represent both scenarios.
Is this correct? If so, is there better solution that creating the last refresh data using Power Query - this is non-ideal as it requires real estate on the report page to display.
https://docs.microsoft.com/en-us/azure/devops/report/powerbi/add-last-refresh-time?view=azure-devops
Thanks
@mahoneypat
@camargos88
@harshnathani
@AllisonKennedy
@FrankAT
@DebbieE
@BA_Pete
@DataZoe
@EricHulshof
@Daviejoe
@DavidWaters100
@fhill
@kcantor
@Pragati11
@ryan_mayu
@ashishrj
@jthomson
@dedelman_clng
@lbendlin
@vivran22
@AntrikshSharma
@mussaenda
@OwenAuger
@nandukrishnavs
Copying DAX from this post? Click here for a hack to quickly replace it with your own table names
Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C
I work as a Microsoft trainer and consultant, specialising in Power BI and Power Query.
www.excelwithallison.com
Thanks Alison, tooltips definitely seems like a good way to go with this realestate limitation - i'll definitely give that go as well as Greg's tooltip suggestion
That coupled with BA_Petes suggestion of just the PQ datetime.FixedLocalNow as a query to avoid whole columns is great; my understanding Pete is that I will import this query and it will represent the import time of the other tables, the DQ data being as current as the last user interaction with the DQ data, so I will not display a refresh time for this.
Cheers all!
@Anonymous ,
I think you understand correctly. The DateTime.FixedLocalNow() query will refresh along with all your other imported queries when you perform a refresh on the dataset in the PBI Service, giving you a pretty good steer on last imported model DateTime. The 'Fixed' part just prevents it from changing during successive calls during execution of an expression.
Pete
Proud to be a Datanaut!
Hi @Anonymous ,
The link you provided is essentially the way that I have displayed last refresh time in reports in the past except that I don't add an entire column into a table for it, I just create a blank query and add the following into the formula bar:
= DateTime.FixedLocalNow()
This can then be used as a field on your report (adjusted for the time zone etc. that you want it to display).
How this would behave in an Import/DirectQuery hybrid model, I have no idea I'm afraid.
Pete
Proud to be a Datanaut!
>sigh< I feel left out.
@Anonymous - I was just joking! Hopefully someone else jumps in here because I do not know of any way around that issue. What you describe is my understanding of how things work and creating your time stamp is the only way I would know how to fix it. If you did not want it to take up space, you could add it to the Tooltips area of your visuals perhaps.
The tooltip is a good suggestion and something I had not considered - cheers Greg!
User | Count |
---|---|
65 | |
27 | |
25 | |
17 | |
11 |