Validation failed
Before a global package is deployed into a target tenant, the global package is validated against the target tenant. Any missing dependencies or compatibility issues in the target tenant are identified and reported.
This topic describes scenarios that can cause the validation to fail. After the issue has been corrected, you should run the validation process again to verify that all issues have been corrected.
Email Template (CMItem: the actual resource file) Not Appearing in Target Tenant
The Global Package Email Templates must be dependent on an Output Template, this is a requirement of the Linking Stage.
Needed Values Sets not found in export package or target tenant
During the linking of any Document Type, the dependencies must be included in the global package.
Needed Values within Value Set Dependencies do not exist
You cannot delete the Value Set values. The Value Set is locked.
Needed Document Types not found in export package or target tenant
During linking of any Content, you must include the dependencies in a Global Package.
Various Attribute changes on Document Type
After a Package Version is created (the export is complete), you need to lock the Document Type attribute.
Validate if display name is present for value set
You must create the Global Package Value Sets from the user interface.