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 API Gateway does not fail the deployment but throws these validation warning messages:

Warning: Suite type {suiteDefinition.SuiteType} with context {suiteDefinition.Context} already existed in tenant {tenantId}, continue importing will overwrite existed suite.

The issue occurs when the target tenant contains the same suite with the same context.

To resolve the issue, acknowledge and overwrite the existing suite with the new deployment content.

Warning: T2V validate for requestId:{validateRequest.requestId}, OAuth2Scope is disabled for Tenant:{tenantId}, Authapp:{item.Name} still importing scopes, user cannot see until scopes enabled for tenant

The issue occurs when the deployment package contains an authorized application with scopes, and the OAuth2.0 toggle is disabled in the target tenant.

To resolve the issue, enable the OAuth2.0 toggle in the target tenant.

Warning: requestId: {validateRequest.requestId} Tenant: {tenantId} with authappname: {item.Name} infor authapp is not existing, will not import this authapp

The issue occurs when the deployment package contains an Infor-cloned application with the API suite not deployed in the target tenant.

To resolve the issue, deploy the Infor-cloned application before deploying the package.

Warning:requestId:{validateRequest.requestId} tenant:{tenantId} with authappname:{item.Name}; cannot import as this is ION infor App

The issue occurs when the deployment contains a Backend Service application with the App name "IONWorkflow". The IONWorkflow is a default application that is provisioned together with ION and cannot be imported through global packages.

Warning:requestId:{validateRequest.requestId} tenant:{tenantId} with authappname:{item.Name} already exits, continue importing by overriding existing authapp

This issue occurs when the deployment package contains an authorized application with the same type and name as in the target tenant. If you deploy the package, the applications in the target tenant are overwritten.