Forum Discussion
Power Apps & Power BI Direct Query
Hi everyone,
I recently upgraded my Power Apps by adding new columns and filters. However, when I refresh in Power BI, I am unable to see the new filters and tables. I made sure to toggle the option to make it available in the dashboard when creating the new columns.
For context, the solution is a model-driven app with data in Dataverse, connected in DirectQuery mode with Power BI.
Has anyone encountered this issue before or have any suggestions on how to resolve it?
Thanks in advance for your help!
Hi Anonymous ,
Apologies for the delay in getting back to you.
Thanks for the update! Sorry to hear you're still running into connection issues.
The error message you're seeing usually means Power BI is having trouble reaching Dataverse (which uses an Azure SQL backend). Here are a few things you can try to fix it:
Steps to Troubleshoot:
- Check Internet or VPN
Make sure you have a stable internet connection and no VPN or firewall is blocking access to your Dataverse environment (e.g., *.crm4.dynamics.com).
- Update Power BI Desktop
Sometimes older versions can cause issues. Please make sure that you downloaded the latest version from Microsoft portal.
- Clear Saved Credentials
In Power BI, go to File > Options and settings > Data source settings, find your Dataverse connection, and clear the credentials. Then try reconnecting.
- Use OData Feed
As a workaround, you can try using the OData feed to connect to Dataverse:
Please check the below document for the more info:
https://learn.microsoft.com/power-apps/developer/data-platform/webapi/overview
- Check Security Roles in Dataverse
Make sure your user has the right permissions to access the new tables and columns via API.
🔗 https://learn.microsoft.com/power-platform/admin/security-roles-privileges
If none of these steps help, I’d suggest raising a support ticket with Microsoft so they can investigate further:
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketIf 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!
Regards,
B Manikanteswara Reddy
6 Replies
Hi Anonymous,
Thank you for reaching out to Microsoft Fabric Community Forum.
It might be due to permission issues in Dataverse. Please ensure that newly created columns and filters are properly published and accessible in Dataverse. If we make any small change in schema , it takes time to reflect.
Since Power BI is not refreshing automatically though its connected through Direct Query mode, try to refresh manually.
Also please make sure that you deleted Power BI cache.
Go to File → Options and settings → Options→ Global settings→ Data Load→Clear Cache
then restart Power BI.
Check the Dataverse connection in Power BI. Try to remove and add the table that connected to the Dataverse , and then check( this is the final option that we have to recheck)
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!
Regards,
Vinay PabbuHello, thanks for you reply and support. Unfortunelty it didn't work and when i tried to reconnect to the dataverse i got this error DataSource.Error: Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Details:
DataSourceKind=CommonDataService
DataSourcePath=org4b85c796.crm4.dynamics.com
Message=A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
ErrorCode=-2146232060
Number=53
Class=20
State=0
ConnectionId=00000000-0000-0000-0000-000000000000So am having a connection problem, do you have an idea how to solve that?
Hi Anonymous ,
Apologies for the delay in getting back to you.
Thanks for the update! Sorry to hear you're still running into connection issues.
The error message you're seeing usually means Power BI is having trouble reaching Dataverse (which uses an Azure SQL backend). Here are a few things you can try to fix it:
Steps to Troubleshoot:
- Check Internet or VPN
Make sure you have a stable internet connection and no VPN or firewall is blocking access to your Dataverse environment (e.g., *.crm4.dynamics.com).
- Update Power BI Desktop
Sometimes older versions can cause issues. Please make sure that you downloaded the latest version from Microsoft portal.
- Clear Saved Credentials
In Power BI, go to File > Options and settings > Data source settings, find your Dataverse connection, and clear the credentials. Then try reconnecting.
- Use OData Feed
As a workaround, you can try using the OData feed to connect to Dataverse:
Please check the below document for the more info:
https://learn.microsoft.com/power-apps/developer/data-platform/webapi/overview
- Check Security Roles in Dataverse
Make sure your user has the right permissions to access the new tables and columns via API.
🔗 https://learn.microsoft.com/power-platform/admin/security-roles-privileges
If none of these steps help, I’d suggest raising a support ticket with Microsoft so they can investigate further:
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketIf 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!
Regards,
B Manikanteswara Reddy
Hi Anonymous ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
B Manikanteswara Reddy