Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
A crazy Power BI idea is in my head. It rather doesn’t make much practical sense, but such crazy ideas sometimes lead to useful solutions for the different problem.
A power BI report that displays its own metadata, including refresh history, including the most recent refresh error if refresh failed.
Crazy enough? Ha!
1) A composite model report with main data sources in import mode and one special table in direct query mode. Published into Power BI service.
2) A scheduled PowerShell* script that uses Power BI Cmdlets / REST API to get the refresh history and to insert it into the database table. Yeah, into the table that already connected to the report in direct query mode.
3) Now the report can display it’s own refresh history, including error details if refresh failed.
Am I crazy enough?
Just a quick test (not fully parsed/formatted):
Hi @avatorl ,
It is an interesting idea, thank you for your sharing.
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.
User | Count |
---|---|
3 | |
3 | |
2 | |
1 | |
1 |
User | Count |
---|---|
11 | |
4 | |
3 | |
3 | |
2 |