However the changeset fails to deploy with errors on the Dashboards and Reports which reference one of the roles saying that one of the Roles could not be found, like:
Dashboard_Reports Folder 6 15 In field: role - no Role named Motoring_Display_Manager found
Performance_Dashboards Folder 6 15 In field: role - no Role named Motoring_Display_Manager found
It seems like the change set is failing to deploy the components with the independent objects first - in this case the Roles before the Dashboards and Reports.
One of the two roles in question has the other role as the parent role (Motoring_Display_Manager is parent of Motoring_Sales) - so perhaps the issue is with the changeset deploying the Roles in the incorrect order?
I did manage to deploy the change set by deploying the Roles first using Eclipse (i was using the same user to deploy the change set as to deploy the Role objects using Eclipse - a System Administrator with View All and Modify All checked, as well as all the change set permissions).
I am wondering if anybody else has experienced this issue or similar before?
Cheers!
Robin Smith
2 respostas
Hi Robin, yes, what you did is correct. Since you cannot choose the order of the deployment when you run into these types of errors it is best to break the deployment into smaller changes sets i.e.
Deploy parent role, then deploy other roles, then deploy the dependent reports and dashboards.
