Forum Discussion
Data gateway support for paginated reports
Hi v-danhe-msft, thanks for the replay unfortunately I can't find this to work.
Currently I have solution wit multiple "standard" reports (.pbix) and with them everything is fine it can reach datasources (in Azure) behind data gateway and now I'm trying to introduce paginated reports and here comes problem as even when I try to connect to data source I get an error:
Failed to update data source credentials: 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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)Hide details
| Activity ID: | 9f11e9be-0178-4be0-a72c-4be05e010e83 |
| Request ID: | a787815d-cd7c-bae7-483c-cac5e8872883 |
| Status code: | 400 |
| Time: | Mon Mar 18 2019 10:01:52 GMT+0100 (Central European Standard Time) |
| Version: | 13.0.8730.162 |
| Cluster URI: | https://wabi-west-europe-redirect.analysis.windows.net |
db is in azure (sql managed instance)
report configuration is:
connection type:
Microsoft Azure SQL Database
connection string:
Data Source=<server url> Catalog=<db name>
credentials are also correct connection works fine with Report Builder but not after deploying to Power BI Service.
Can you give me some hint what I'm doing wrong maybe I should update connection string somehow?
Best regards,
Michał
michalg,
I got the same requirement and problem as you have. Do you find any solution yet?
James
hi jcheng, unfortunately in my scenerio it's not working by I'm using Qzure SQL Managed Instance as db source, I found it working in another solutions what you have to do is to change SQL instead of Azure SQL as connetion type in your report datasource configuration.
I am able to find a solution for this pagenated report in connecting to SQL MI database. You will need to create CNAME in your local DNS for SQL MI server which is FQDN by default. The CNAME could be just the first part of FQDN. Then, the Power BI report builder will use the CNAME instead of FQDN as SQL data source. The Report builder will try this CNAME as local SQL server instead of Cloud/Azure SQL server. After publishing pagenated report to Power BI App Workspace, you need to specify the rigt Gateway for this connection. Then, the pagenated report should run fine.
James
I have checked with Microsoft on this gateway support for paginated reports. At this moment there is no gateway support and there is no roadmap for the same in 2020. Also it is already called out in the microsoft documentation https://docs.microsoft.com/en-us/power-bi/paginated-reports-data-sources
The other option on hand is to use a power bi dataset sourced from Azure or other data sources refreshing via gateway. Also there is a limitation there, you cannot connect to the power bi dataset having live connection. You can do it on the dataset having direct query or import or composite models.
Hope this helps!