When deploying artifacts in the Tenant Manager, validation is performed before items are published to the target environment. If a validation error occurs, the deployment status and artifact states will be updated to reflect the failure.
Validation Failure Statuses #
When a deployment encounters validation issues, the following occurs:
- Deployment status: The overall deployment moves from In Progress to Not Deployed.
- Offending item status: The specific artifact(s) causing the error are marked as Validation Failed.
- Other items: All artifacts that successfully passed the validation check will be marked as Not Deployed, since the deployment cannot be completed until the failed items are corrected.
Common Causes of Validation Failure #
The most frequent reason for validation failure is when an artifact’s Display Name or System Name (for example, in Data Blocks or Data Objects) is already in use by another artifact in the target tenant.
This typically happens when artifacts are created manually in both environments instead of being migrated through Tenant Manager. As a result, duplication of names prevents deployment.
Solution #
To resolve this issue:
- Delete or rename the artifact in either the target tenant or the source tenant to remove the conflict.
- Once corrected, redeploy the item using the Tenant Manager.
Special Note for Legacy Clients #
Some legacy clients may encounter validation errors specifically with older Data Objects created prior to January 1, 2025. If this occurs, please contact Assette Client Service for assistance in resolving the issue.