Error Symbol on All Tables in Semantic Model

[brianarwiley]

Every table in my semantic model has this red triangle with an arrow in it. How do I find out what is causing this? I think it's related to why my dashboards aren't updating with new data, even though my lakehouse tables are up to date. Last week our Fabric admin left the company and his credentials were changed to a service account, so that could be part of the problem, but I don't know where to look to correct whatever the issue is. 

[v-csrikanth · Accepted solution]

Hi @brianarwiley 
Can you give a try the below steps to resolve the issue:

• Go to Manage Connections and Gateways in your workspace.

• Create a new Lakehouse connection using Azure Active Directory authentication tied to the updated service account.

• Open your semantic model settings in the workspace and replace the default data source connection with the newly created one.

• Ensure this new connection uses explicit credentials, not SSO.

• Refresh the semantic model manually and verify if the issue is resolved.

Creating a new connection and explicitly assigning it ensures your semantic model has valid credentials to access the Lakehouse data post-admin transition.

If the above information helps you, please give us a Kudos and marked the Accept as a solution.
Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth]

HI @brianarwiley 

I wanted to follow up since I haven't heard from you in a while. Have you had a chance to try the suggested solutions?
If your issue is resolved, please consider marking the post as solved. However, if you're still facing challenges, feel free to share the details, and we'll be happy to assist you further.
Looking forward to your response!

Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth]

HI @brianarwiley 

I wanted to follow up since I haven't heard from you in a while.If your issue is resolved, please consider marking the post as solved. However, if you're still facing challenges, feel free to share the details, and we'll be happy to assist you further.
Looking forward to your response!

Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth]

Hi @brianarwiley 
Thanks for the confirming that your issue has been autoresolved.
Please do reach out to the Fabric community if you have any further new issues.

If the above information helps you, please give us a Kudos and marked the Accept as a solution.

Best Regards,
Community Support Team _ C Srikanth.

[brianarwiley · Accepted solution]

So far nothing has fixed this. My tables seem to be updating appropriately so for now I am going to assume it's a random glitch. 

[v-csrikanth]

Hi @brianarwiley 

We haven't heard from you since last response and just wanted to check whether the solution provided has worked for you. If yes, please Accept as Solution to help others benefit in the community.
Thank you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth · Accepted solution]

Hi @brianarwiley 
Can you give a try the below steps to resolve the issue:

• Go to Manage Connections and Gateways in your workspace.

• Create a new Lakehouse connection using Azure Active Directory authentication tied to the updated service account.

• Open your semantic model settings in the workspace and replace the default data source connection with the newly created one.

• Ensure this new connection uses explicit credentials, not SSO.

• Refresh the semantic model manually and verify if the issue is resolved.

Creating a new connection and explicitly assigning it ensures your semantic model has valid credentials to access the Lakehouse data post-admin transition.

If the above information helps you, please give us a Kudos and marked the Accept as a solution.
Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth]

Hi @brianarwiley 
Could you please confirm the roles assigned to you at both the workspace level and for the Lakehouse and report permissions?
Please share the what is the warning shows on the data source.

Best Regards,
Community Support Team _ C Srikanth.

[brianarwiley]

Permissions are admin with a premium license. The error doesn't say anything, which is part of my problem. I mouse over it or click on it and it's almost like there is nothing to click on. 

[v-csrikanth]

Hi @brianarwiley 
Thank you for being part of the Microsoft Fabric Community.

The red triangle with an arrow icon indicates a broken connection to your data source, likely due to the recent admin credential change.

To resolve it:

• Check Credentials: Go to Workspace > Datasets > Settings > Data source credentials.
  Re-authenticate using the new service account if needed.

• Verify Gateway Access (if used): Ensure the gateway is online and the new service account has access.

• Reconnect Lakehouse (if applicable): In Power BI Desktop, go to Transform Data > Data source settings and update the Lakehouse connection.

• Refresh Dataset: After updating credentials, go to Power BI Service > Datasets and run a Refresh now.

This should restore the connection and fix the update issues in your reports.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

[brianarwiley]

Sorry, I feel dumb but I'm in Fabric app.powerbi.com/home?experience=fabric-developer and in the workspace I am not finding #1 at all. Can you screenshot where that's supposed to be? Everything I am doing is in Fabric/PBI online and none of it is using desktop. Also this is the default semantic model in this Warehouse, and this is happening in all the lakehouses in my warehouses. 

*EDIT* Also I created a new semantic model and the tables are not throwing errors and seem mostly fine which has me even more confused.