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.

At this time, there are no known validation failures, however, you may see the Evaluate status returned for some resources.

Object schema exists with the same name, but different type

If an object schema with the same name exists in the target tenant as a different object type, the Evaluate status is returned.

To resolve the issue, you must accept and acknowledge the warning before proceeding with the deployment. If the existing schema is no longer required, you can delete it from the target tenant before proceeding with the deployment.

Schema extension is in use by another schema file

If a schema extension included in the package is using a different schema file in the target tenant, the Evaluate status is returned.

To resolve the issue, you must accept and acknowledge the warning before proceeding with the deployment. If the extension is no longer required in the target tenant, you can remove it from the tenant before proceeding. If the schema extension is not removed from the target tenant, the extension in the file is skipped and will not be imported.