The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi Dear,
i have this issue when i open my power bi desktop for 2 projects only
Solved! Go to Solution.
Open your PBIX file and look for:
Yellow warning triangles in the Fields pane
"Refresh error" notifications with object names
Greyed-out measures/columns
Go to Transform data → Data source settings
Click "Edit Permissions" and look for red error indicators
Check each query in Power Query Editor for:
Source steps showing errors
Removed columns (will show as "Invalid")
// Paste this in Advanced Editor to find broken dependencies let AllQueries = #shared, QueryList = Record.ToTable(AllQueries), StatusCheck = Table.AddColumn(QueryList, "Status", each if Value.Is([Value], type table) then try Table.RowCount([Value]) otherwise "BROKEN" else "Not a table") in Table.SelectRows(StatusCheck, each [Status] = "BROKEN")
Use SQL Server Profiler to capture queries from Power BI
Check the "Defective Objects" collection in SSAS error logs
Run a schema compare in Visual Studio if you have the original model
Version comparison: If you have an older working PBIX, use a diff tool to compare files
Metadata inspection: Rename .pbix to .zip and examine DataModelSchema for errors
Last resort: Recreate the connection while keeping visuals (use "Keep visuals" option when replacing datasource)
Set up database change alerts
Use consistent naming conventions
Consider using a staging layer (views/synonyms) to abstract direct dependencies
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you.
Please advise , what I can do ?
Open your PBIX file and look for:
Yellow warning triangles in the Fields pane
"Refresh error" notifications with object names
Greyed-out measures/columns
Go to Transform data → Data source settings
Click "Edit Permissions" and look for red error indicators
Check each query in Power Query Editor for:
Source steps showing errors
Removed columns (will show as "Invalid")
// Paste this in Advanced Editor to find broken dependencies let AllQueries = #shared, QueryList = Record.ToTable(AllQueries), StatusCheck = Table.AddColumn(QueryList, "Status", each if Value.Is([Value], type table) then try Table.RowCount([Value]) otherwise "BROKEN" else "Not a table") in Table.SelectRows(StatusCheck, each [Status] = "BROKEN")
Use SQL Server Profiler to capture queries from Power BI
Check the "Defective Objects" collection in SSAS error logs
Run a schema compare in Visual Studio if you have the original model
Version comparison: If you have an older working PBIX, use a diff tool to compare files
Metadata inspection: Rename .pbix to .zip and examine DataModelSchema for errors
Last resort: Recreate the connection while keeping visuals (use "Keep visuals" option when replacing datasource)
Set up database change alerts
Use consistent naming conventions
Consider using a staging layer (views/synonyms) to abstract direct dependencies
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you.
Hi @SherifHassan
If the response addressed by you received was helpful in resolving your issue, we would greatly appreciate it if you could mark it as the Accepted Answer. This action not only assists you but also benefits others in the community who may encounter similar challenges.
Should you have any further questions or require additional assistance, please don’t hesitate to provide more details. We’re always here to help!
Thank you for your continued engagement in the Microsoft Fabric Community!
Hi @SherifHassan
I wanted to follow up regarding your issue with opening Power BI Desktop for the two specific projects. I understand how important it is to resolve this matter promptly.
If you have had a chance to troubleshoot or review any suggestions provided, I would appreciate your feedback. If the solution worked for you, please consider marking it as accepted to help others in the community.
If you still have questions or need further assistance, please feel free to reach out. I'm here to help!
Thank you for your engagement!
Hi @SherifHassan
I wanted to follow up regarding the issue you reported with Power BI Desktop for the two specific projects.
To ensure we address this matter effectively, please provide any additional details or error messages you may be encountering. This information will help us expedite the resolution process.
If you’ve had a chance to review or try the suggestions provided by @Elena_Kalina , I’d love to hear your feedback.If the solution resolved your issue, please consider marking it as accepted this can help others in the community who may face a similar challenge.
If you still have questions or need further assistance, feel free to let me know. I’m here to help!
Thank you for your engagement!
If the names of tables, columns, measures, or other objects in the source database or cube (e.g., SQL Server, SSAS, Oracle, etc.) have been modified, and your Power BI report references those objects, this may cause the "Unsupported Annotation name 'PBNtFormatHint'" error or other issues when opening the file.
User | Count |
---|---|
75 | |
70 | |
40 | |
30 | |
28 |
User | Count |
---|---|
104 | |
95 | |
51 | |
50 | |
46 |