Validation failed
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.
Stream pipeline exists and is running in the target tenant
If a stream pipeline already exists in the package and is running in the target tenant, the resource can't be overwritten in the target. The import of that stream pipeline fails.
To resolve this issue, stop the existing stream pipeline in the target tenant. Otherwise, the package resource isn't deployed to the target tenant. All other issue-free resources are imported successfully.
Stream pipeline exists in the target tenant with a different object name
If the package's stream pipeline already exists in the target tenant but with a different object name, the object name can't be overwritten in the target tenant. Object names can't be changed for stream pipelines that have been active at least once. As a result, the import succeeds, but the object name isn't updated.
To resolve this issue, delete the existing stream pipeline in the target tenant. Otherwise, the package resource is deployed but the object name isn't updated. All other issue-free resources are imported successfully.
Security role that is associated with a security profile doesn't exist in the target tenant
If the Infor OS security role that is associated with a profile doesn't exist in the target tenant, the package is assigned the Evaluate status. Before the deployment, warning acknowledgment is required.
You can add the missing security role to the target tenant before or after the package deployment. If you deploy the package before you add the role, the security profile is imported and a warning about the missing role and the requirement to add the role to the tenant is displayed.
Security profile includes an object that doesn't exist in the target tenant
If a security profile contains security settings for an object that doesn't exist in the target tenant, the package is assigned the Evaluate status. We recommend that you register the object's schema in Data Catalog before the deployment. Otherwise, the security profile is imported without the object's security settings.
Security role already in use by another profile in the target tenant
If the security role that is associated with a profile in the global package already has a security profile in the target tenant, the package is assigned the Evaluate status. You must acknowledge the warning before you deploy the package.
Before you proceed, review the existing security profile in the target tenant and determine whether to retain it or replace it with the profile included in the package.
To use the security profile from the package, delete the existing profile from the target tenant, provided that the target tenant's profile is not a resource from another global package.
If you can't delete the existing security profile and proceed with the deployment, the import for that resource fails. Other security profiles without conflicts are imported successfully.