Forum Discussion
Pushing Report created from using Dataflow from Dev to Prod
Hi All,
Can I please seek clarification in terms of the subject listed.
My question is: Do we MUST retain a copy of the report (that was created in DEV using the Dataflow) in both DEV and TEST once it is pushed to PROD.
Appreciate the input.
Duplicating a PROD report into DEV/TEST for modifications and republishing it to PROD will not break the link if:
- The dataset remains the same (or you rebind the report to the correct PROD dataset before publishing).
- You overwrite the existing PROD report (instead of creating a new one) to maintain the report GUID.
Potential Issues:
- If DEV/TEST uses a separate dataset and the report isn’t updated to link to the PROD dataset before publishing, problems may occur.
Suggested:
- Duplicate the PROD report into DEV/TEST.
- Make modifications in DEV/TEST.
- Before republishing, ensure the report is linked to the correct PROD dataset.
- Overwrite the existing PROD report (don’t create a new one).
This ensures the link remains intact and avoids issues.
10 Replies
No. DEV, TEST and PROD are artificial constructs to support your development methodology. They are not required by the report user consuming your report.
Hi Marshmallow
Yes, you can remove the report from DEV and TEST after pushing it to PROD, but keeping it has benefits like audit traceability, rollback in case of issues, future updates, and compliance. If storage is a concern, consider archiving instead.
Note: Check your organization's policies and best practices before removing DEV/TEST reports.If this response was helpful, please accept it as a solution and give kudos to support other community members
Hi, won't archiving also taking up storage? Also, what is the best protocol if we need to update the visualisation if we have deleted the dev/test reports.
You're correct that archiving consumes storage, but it's often a more efficient and structured approach for managing older or less frequently accessed reports compared to keeping them in active environments.
If you've deleted the DEV/TEST reports and need to update visualizations, here are some options:
- If the PROD report is stable, use it as a reference and duplicate it back into the DEV/TEST environment for modifications.
- If no backup exists, recreate the report in DEV or TEST using the available datasets and business logic.
Hi Marshmallow,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like you want to know if you can/should keep a copy of the report in both DEV and TEST after pushing the same to the PROD. As ArwaAldoud and lbendlin both responded to your query, please go through their responses and accept the helpful response as solution.
I would also take a moment to thank ArwaAldoud and lbendlin, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi Marshmallow,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.Hi Marshmallow,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.
Thank you.
