I am working on a project that involves deploying a sequence of Managed Packages and unmanaged packages (using an ant deployment).
As I was onboarded to the project, I noticed the unmanaged package.xml with the unmanaged metadata had a
<fullName> field. This naming convention is causing an issue when we try to deploy certain metadata changes to items that came from the managed package.
- Managed Package is deployed into the org with a report folder (NAMESPACE__Managed_Report_Folder)
- Unmanaged package (with fullName field) is trying to update the managed report folder by granting shares to a public group in the meta.xml file for the report folder
- When using ant to deploy the unmanaged package, I receive the following error:
Error: Cannot add component of type:ReportFolder named:NAMESPACE__Managed_Report_Folder subjectId:SOME_FOLDER_ID to another package because it is an installed component.
So this begs the question: Can I somehow avoid this error when deploying my unmanaged metadata?
Is the only solution to remove the fullName field in the package.xml?
When should I be using a fullName field in my package vs not including that field and what is the benefit I get out of including a fullName for my package.xml?
Any help is much appreciated!