OAuth token refresh fails intermittently when pbi on server refrehses
Situation: Data source connection failed and visuals doesn't work as expected in pbi on Server. Root causes: OAuth token refresh fails intermittently on PBI server. Questions: how do I get UAuth token expiration in advance? Do we have a workaround to avoid it?
how to change the service account in On Prem gateway
Hello everyone ! I am trying to connect a network directory using Power Automate . As you know the first step is to install and register gateway . I did the same but to connect to network folder/ directory - I got to know that we need to change the service account present in Service Settings ! I tried to change with my Windows User name and password , it is continuously throwing password / user incorrect error . Can you please guide me what needs to entered in Service Setting --> Change Service Account ? Please note that we have dedicated service account and I am trying to use the same ..
Report access issue — Read-permission users unable to view Power BI report
Setup / Architecture: The base semantic model resides in a Production workspace. A local (composite) semantic model is built on top of this base semantic model via DirectQuery, and sits in a different workspace along with the report built on it. So the chain is: Base Semantic Model (Production workspace) → Local/Composite Semantic Model + Report (separate workspace) Access configuration already done. - A security group was created. - This security group has been added with permissions to all three items in the chain: - The Power BI report - The local/composite semantic model - The base semantic model The problem - Users with Member access to the workspace(s) can open and view the report without issue. - Users who only have Read access (via the security group) cannot view the report — they hit an access error when opening it.Semantic model refresh failed - Snowflake Key Pair cloud connection
Hello everyone! I have multiple Power BI semantic models that refreshes via Power Automate. The model connects to Snowflake using a shareable cloud connection with Key Pair authentication (no on-prem gateway). This morning I got several refresh failures with: We are unable to access some data source because the artifact is missing connection details. Please contact the artifact owner to bind the data source to a data connection or use default connection settings for the unbound data source. Refreshes appear to be working again now and it worked automatically for some models at the same time others failed. I didn't change the Key Pair, the cloud connection, or the semantic model binding. What typically causes this error with a Snowflake Key Pair cloud connection? Is this an unbound data source (binding lost) rather than invalid Key Pair credentials? How can I prevent this from happening again (permissions on the connection, avoid Default/Personal mapping, re-bind after publish, etc.)? Thanks!
Avoid showing broken visuals in apps during report deployment and refresh
Description: When we move a report through environments (Dev → UAT → Prod), the corresponding app can temporarily display broken visuals. This typically happens in the window between deploying the updated report and completing the first dataset refresh, and then updating the app. During this period, users who open the app may see broken visuals or errors, which creates confusion and the impression that the report is not working. Desired behaviour: It would be very helpful if the app could continue to serve the previous, fully working version of the report until: The new report version has been fully refreshed, and The app has been updated successfully. Only after these steps should users see the new version. In other words, we would like a “graceful switchover” model where: The old report version remains visible and functional in the app while the new version is deploying and refreshing in the background. Once the refresh completes successfully, the app is updated and starts showing the new version to users. Benefits: Prevents users from seeing broken visuals or partially updated reports. Reduces confusion and support tickets caused by temporary breakages during deployment. Allows BI teams to follow proper deployment practices (Dev → UAT → Prod) without impacting user experience. This feature would greatly improve reliability and user trust in Power BI apps during deployment and refresh cycles.
