User Account Specific Validation Errors
When deploying objects such as reports to a Target ORG, sometimes the reports are shared with a user in the source ORG. If the user does not exist in the Target ORG, the validation throws an error. Would it be feasible to add objects, such as reports, to the Warnings / Fixes screen so we can easily select how to handle user specific dependencies? Maybe we can chose to enter a new username or simply remove the shared with permission on the object?
Richard Scott
shared this idea
-
Richard Scott
commented
You're welcome.
I apologize for the delay as I have been out of the office for a bit. Yes, this matches my experience pertaining to shared reports. It is the actual folder where the permissions are located. However, I will need to validate that creating the folder in the target ORG will make the reports push through. I will let you know how that goes for me within a day or two.
Thanks!
Richard
-
Hi Richard,
Thanks for the feedback - I think I've reproduced this issue. Am I right in thinking that in case of reports it's actually the report folder which has the invalid sharing rule?
I've done the following:
- Created a new report folder called "Shared folder", and shared it with a user that only exists in my source org
- Created a new report in that folder
- Attempted to deploy the report to the targetAt this point, Gearset warns me that I haven't included the report folder, and I tick the box to include it. The deployment now fails because the report folder is shared with a user that doesn't exist in the target.
I managed to make the deployment go through by manually creating the same folder in the target, so that Gearset only needs to deploy the report.
Does that match your experience?
