Forum Discussion
Helper IIPushing Report created from using Dataflow from Dev to Prod
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.
Helper III was being advised by my colleague if I use the prod report as a reference and duplicate it back into the DEV/TEST env for modifications and re-push it back to the Prod, it will break the link....I haven't tried this myself but i am trying to understand it.
I was thinking to apply the same concept (opt. 1) you listed but being opposed by collague. So I am seeking confirmation :).
Super UserDuplicating 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.