New report not functioning in Production workspace of Deployment Pipeline

[RandyPgh]

I have a new report that pulls data from dataflows and functions fine in Desktop and in Development and Test workspaces of a Deployment Pipeline. When deploying the report to Production, however, the dataflow GUIDs seem to fail to switch to Production. A refresh of the Production semantic model is clean (no errors), yet there is no data in the report. Other reports continue to function in the Production workspace.

To investigate the issue, I did the following:

• I downloaded the Production report and opened it in Desktop. All tables are empty, and the GUIDs are still pointing to the Test workspace. I did pull the Test PBIX, also, just to be sure that its GUIDs were pointing to Test. They are.
• Although a new report, I have tried deleting the report from Production and Test to republish. I also refreshed the data in Test prior to deploying to Production, just in case that would help. Nothing has fixed the issue.

[Anonymous]

Hi @RandyPgh ,

May I ask if this has been resolved? If so, is it possible to share your solution?

Thank you.

Best Regards
Community Support Team _ Rongtie

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[RandyPgh]

Thanks for the suggestions. I will work with my internal administrators to see if they have a solution or want to push it up to a Microsoft support ticket.

[GilbertQ]

Hi @RandyPgh 

Can you confirm that you have put in their parameters for the different data flows when you are moving your deployment pipelines from test to prod?

Create deployment rules for Fabric's Application lifecycle management (ALM) - Microsoft Fabric | Mic...

[RandyPgh]

I have not needed to enter parameters for the dataflows. For the 15 other reports that I have deployed, the tool just understood that dataflow GUIDs needed to be changed to the new environment. The tool also changed the GUIDs from dev to test, just not from test to prod.

[GilbertQ]

Hi @RandyPgh 

Must be a bug or could you try and create it again?