Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi,
I have a paginated report in production workspace which pulls live data from a parquet file which is not working after publishing.
What could possibly be the issue and how can we fix it?
The report works in the dev environment workspace perfectly though
I have attached the error message.
Any suggestions or solutions on this will be highly helpful.
Thanks in advance!
Solved! Go to Solution.
Have you alrrady tried another file in the same container. Maybe not a parquet but a simpler one to verify it's not a network/permission issue.
i assume you're using power query inside paginated reports. If yes remember it's in preview, maybe you're facing a bug.
try to delete and upload report back to the service.
last option support case to msft.
Hi @Ashwath_Bala_S ,
The issue you are facing may be due to configuration or environment settings between your development and production workspaces.
Identify any differences between the development and production environments that could impact the report, such as data source configurations, regional settings, or custom settings specific to the production environment.
Verify the data source connection in the production environment is properly configured and accessible, as network configuration differences or firewall settings can sometimes lead to connectivity problems.
Try running the report in the production environment directly from Power BI Desktop to see the problem is with the report itself or the environment.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Thank you.
Hi @Ashwath_Bala_S ,
The issue you are facing may be due to configuration or environment settings between your development and production workspaces.
Identify any differences between the development and production environments that could impact the report, such as data source configurations, regional settings, or custom settings specific to the production environment.
Verify the data source connection in the production environment is properly configured and accessible, as network configuration differences or firewall settings can sometimes lead to connectivity problems.
Try running the report in the production environment directly from Power BI Desktop to see the problem is with the report itself or the environment.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Thank you.
Have you alrrady tried another file in the same container. Maybe not a parquet but a simpler one to verify it's not a network/permission issue.
i assume you're using power query inside paginated reports. If yes remember it's in preview, maybe you're facing a bug.
try to delete and upload report back to the service.
last option support case to msft.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 7 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 13 | |
| 5 | |
| 3 | |
| 3 | |
| 2 |