OData Failed to test the connection to your data source After Publish of Semantic Model

[Dr3Bob]

I have a semantic model with several OData connections.  When I publish updates to the model and look at the Data source credentials in settings, all of them are showing an issue (triangle with !).  I have to edit each one and login again with my account to clear the issue and enable refresh.  Since the account has not changed nor the password the existing OAuth2 credentials should still work.  Why should I have to do this after making small updates to the queries in the model? Also, since all the connections are to the same D365 base URL why are there separate connections for each one?  I should only have to enter the credentials once for all the connections because they are all going to the same place.

[pallavi_r]

Hi @Dr3Bob ,

Independent connection setting for same data sources provided probably to give flexibility on privacy settings (Private/Organization/Public etc) This is to control data sharing and security for each of these datasets independently for us to decide which dataset needs to be isolated and which dataset can be combined.

Thanks,

Pallavi

[Dr3Bob]

Thanks, @Akash_Varuna for your post explaining how the system currently works and for suggesting alternative authentication methods.  However, that was not the intent of my post.  My intention was to suggest that the current functionality could be improved by not treating updated queries as new and consolidating the credentials for OData queries that use the same base URL.

Your suggested solutions do not work for our environment so they are not acceptable solutions.

[v-mdharahman · Accepted solution]

Hi @Dr3Bob,

As you mentioned your intent was to suggest Microsoft about improvement in the functionalities, you can go through the below link and submit your idea for making a change in the curent functionality of OData queries.

Fabric Ideas - Microsoft Fabric Community

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[v-mdharahman]

Hi @Dr3Bob,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are facing an issue when publishing updates to a Power BI semantic model with multiple OData connections. As @Akash_Varuna, already responded to your query, please go through the response provided and mark it as solution if it helps in solving your issue.

I would also take a moment to thank @Akash_Varuna, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[Akash_Varuna]

Hi @Dr3Bob This occurs because Power BI treats modified queries as new, invalidating existing OAuth2 tokens. Switching to a Service Principal or Managed Identity can ensure persistent authentication.

Power BI treats each OData query as a separate connection due to different paths or parameters. To avoid this, consolidate queries using a single connection or centralize them in a dataflow. Use a gateway for easier credential management and optimize queries to minimize changes.