Validation failed

Before a local package is deployed into a target tenant, the local 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.

Validation fails when Document Processor flow has same name

Validation fails if the target tenant already contains a Document Processor flow with the same name as the source tenant.

You can resolve this by ensuring the flow in the source tenant has a unique name. Before creating a new flow in the source tenant, verify the flow names in the target tenant to avoid duplication.

If the flow has the same GUID, it overwrites the existing flow in the target tenant.

Validation fails when IDM attributes mapped to a Document Processor flow

As Document Processor does not support Infor Document Management with local packages, ensure that Document Management attributes are not mapped to document class entities when creating a Document Processor flow.

Otherwise, a validation error occurs when exporting the local packages.