Configuration Migration Errors & Warnings

See the information below for help troubleshooting errors and warnings that occur when deploying configuration migration packages.

Common Warning Messages

Component Type	Warning Message	Explanation	Action
Object	Standard sub-component [lifecycle__v] ignored Standard sub-component [state__v] ignored	Occurs when a migrated object references an object lifecycle does not yet exist on the target Vault. When this occurs, Vault creates a placeholder lifecycle.	Update the placeholder object lifecycle either by migration package or by manual configuration. If you've included the object lifecycle in the same package, you can ignore this message.
Tab	GEN-WCRE-II-1033 – Value for attribute [parent] ignored	Occurs when the package creates a top-level custom tab because the value for parent is blank.	You can ignore this message.
Doctype	GEN-WREC-WG-1065 – placeholder [Doclifecycle. doclifecycle_name__c] was created	Occurs when a Doctype references a document lifecycle that does not yet exist on the target Vault. When this occurs, Vault creates a placeholder lifecycle.	Update the placeholder document lifecycle either by migration package or by manual configuration. If you've included the document lifecycle in the same package, you can ignore this message.
Doctype	Invalid value [Docfield.field_name__c] specified for attribute [fields] : Invalid DocField filter key	Occurs when a Doctype references a document field that does not yet exist on the target Vault.	Add the missing document field to the target Vault either by migration package or by manual configuration. Verify that the field is correctly assigned to the Doctype after deployment.
Doclifecycle	GEN-WADDS-WG-1065 – placeholder [Workflow.review_template1__c] was created	Occurs when a Doclifecycle references a document workflow that does not exist on the target Vault. When this occurs, Vault creates a placeholder workflow.	Update the placeholder workflow either by migration package or by manual configuration. If you've included the workflow in the same package, you can ignore this message.
Atomicsecurity	GEN-W-II-1102: Component renamed to [{object}{lifecycle}{state}]	Occurs when Atomic Security configuration occurred before Vault implementing a new naming pattern	You can ignore this message.

Common Error Messages

Component Type	Error Message	Explanation	Action
Any	GEN-FCRE-ONA-1018 – [standard/application/sample] components cannot be created GEN-FADDS-ONA-1019 – [standard/application/sample] sub-components cannot be created	Occurs when the package contains a standard (__v), application standard (__rim, etc.), or sample (__vs) component/subcomponent that does not exist the target Vault. You cannot create standard components through configuration migration packages.	Skip this component.
Objectlifecycle	OLC-FREC-ONA-1017 – Component is in-use	Occurs when the package removes an object lifecycle state which is referenced by an object or an object workflow.	Manually edit the object configuration and/or object workflow configuration to remove any references to the lifecycle state.
Objectworkflow	GEN-FADDS-II-1035 – value [capa_required__c] for attribute [deviation__qdm] is invalid WFL-FADDS-II-11401 – Field [{object name}.{field name}] does not exist	Occurs when the workflow references an object field that does not exist on the target Vault.	Deploy the updated objects before deploying the current component.
Object	GEN-FADDS-II-1007 – Component already exists with attribute [inbound relationship name], value [{inbound relationship name}]	Sometimes occurs when deploying an object that has two inbound relationships from the same object. This is a valid configuration, but is not supported via MDL/Configuration Migration Packages.	Recreate the object relationships manually in the target Vault.
Object	GEN-FREC-ONA-1017 – Component is in-use: [lifecycle state entry criterion] GEN-FREC-ONA-1017 – Component is in-use: [WorkflowTask]	Occurs when the package removes an object field which is referenced by another component, for example, an object workflow task or lifecycle state entry criteria.	Manually edit the object lifecycle state configuration and/or workflow task configuration to remove any references to the object field. Manually delete the field on the target Vault.
Object	GEN-FADDS-II-1022 – value [{object name}] does not resolve to valid active [object] GEN-FADDS-II-1035 – value [{object reference field name}] for attribute [controlling_field] is invalid	Occurs when the object references another object that does not exist in the target Vault, for example, the inbound package object includes a reference filter that uses a nonexistent object.	Deploy the required object before deploying the current component. Ensure that the target Vault has the correct features enabled because some features automatically provision objects.
Object	OBJ-FREC-ONA-7070 – Cannot disable object types feature when the object has custom object types.	Occurs when the package turns off object types for an object that already includes custom object types in the target Vault.	Manually edit the object configuration to delete custom object types.
Object	OBJ-FREC-ONA-7001 – number of custom objects {#} exceeds [max: 20]	Occurs when your Vault has reached the limit for custom objects.	If appropriate, request a limit increase via Veeva Support.
Object	GEN-FADDS-II-1057 – [Picklist] value is expected	Occurs when the object references a picklist which doesn't exist on the target Vault.	Deploy the picklist before deploying the current component.
Pagelayout	LYT-FREC-ONA-10015 – A layout already exists for the specified object LYT-FREC-ONA-10002 – Controller reference cannot be changed	Occurs when there is a name mismatch for a specific object page layout between the source and target Vaults. You can only have one page layout per object.	Contact Veeva Support to discuss renaming layouts to address the name mismatch. Contact Veeva Support to discuss renaming layouts to address name mismatch.
Pagelayout	GEN-FREC-II-1022 – value [{object field name}] does not resolve to valid active [vault:page.vault:section. vault:detailform.vault:field.reference]	Occurs when the object page layout refers to an object field that does not exist on the target Vault.	Deploy the updated object configuration before deploying the current component.
Pagelayout	LYT-WREC-ONA-10010 – Standard section [workflow_timeline__v] cannot be modified or removed LYT-WREC-ONA-10010 – Standard section [attachments__v] cannot be modified or removed	Occurs if you have disabled lifecycles or attachments on an object in the source Vault but have not migrated those changes to the target Vault before deploying object page layout changes.	Deploy the updated object configuration before deploying the current component.
Docfield	GEN-FREC-II-1036 – Unknown component [{object name or picklist name}]	Occurs when the document field references an object or picklist that does not exist on the target Vault.	Deploy the object or picklist configuration before deploying the current component.
Workflow	Workflow flag is off	Occurs when the Workflow Import Export feature is not enabled on the target Vault.	Contact Veeva Support to request feature enablement.
Docfield	GEN-FREC-II-1030 – Enum list does not contain values: [{field layout section name}]	Occurs when the document field is in a field layout section that does not exist in the target Vault.	Manually create the new field layout section from Admin > Configuration > Field Layout. The layout section name must exactly match the name in the source Vault.
Objectworkflow	GEN-FADDS-II-1022 – value [{object message name}] does not resolve to valid active [notification]	Occurs when the workflow references an object message (Notificationmessage) that does not exist on the target Vault.	Deploy the object message (Notificationmessage) configuration before deploying the current component.
Objectlifecycle	OLC-FREC-II-12518 – cannot resolve rules as the associated [OBJECT] has not been set	Occurs when the lifecycle is not yet associated with any object in the target Vault.	Deploy the updated object before deploying the current component.
Objectlifecycle	GEN-FREC-II-1023 – value [ssu_contracts_leads__c] does not resolve to a valid [Applicationrole]	Occurs when the object lifecycle role references an Application Role that doesn't exist in the target Vault.	Use Vault Loader to load Application Role object records.
Doctype	Invalid value [group:Group.{group name}] specified for attribute [create_document_permissions] : valid active [Group] is expected	Occurs when the document type security configuration references a group that doesn't exist on the target Vault.	Use Vault Loader to load user groups to the target Vault before deploying.
Doctype	Invalid value [{picklist value name}] specified for attribute [etmfDepartmentName_b]	(eTMF, Study Startup only) Occurs when the Department reference does not map to a valid department in the picklist.	Deploy the updated picklist before deploying the current component.
Notification- template	GEN-FREC-II-1034 – Tokens [{object/document field name}] are invalid	Occurs when the document or object message references fields that do not exist on the target Vault.	Deploy the new document fields or updated object before the current component.
Doctype	Invalid value [vdc__29] specified for attribute [clinical_docs_rm] : Invalid hierarchy external ID	(eTMF, Study Startup only) Occurs when the clinical reference model is not enabled on the target Vault.	Contact Veeva Support to enable Study Startup. This will provision the reference model data.
Doclifecycle	GEN-FREC-II-1023 – value [ssu_contracts_leads__c] does not resolve to a valid [Applicationrole]	Occurs when the document lifecycle role references an Application Role that doesn't exist in the target Vault.	Use Vault Loader to load Application Role object records.
Doclifecycle	GEN-FREC-II-1005 – Sub-component [{document field name}] is missing	Occurs when the lifecycle references a document field (as a lifecycle state entry criteria, etc.) that does not exist in the target Vault.	Deploy the new document fields before the current component.
Objecttype	OTP-FADDS-II-18005 – Object [{object name}] does not have field [{object field name}]	Occurs when the object type references a field that does not exist on the object in the target Vault.	Deploy the updated objects before the current component.
Objecttype	GEN-FDROS-ONA-1021 – [standard] sub-components cannot be deleted OTP-FREC-ONA-18011 – Cannot edit the properties of base__v object type field [{field name}]	Occurs when deploying the default base__v object type for any object. This object type is system-managed and created automatically by Vault when you create the object.	Skip this component.
Object	GEN-FREC-ONA-1017 – Component is in-use	Occurs when the package deletes or renames an object field that contains field values in the target Vault.	If renaming a field, rename the field manually on the target Vault and redeploy. If deleting a field with data, you cannot complete this action. Instead, set the field to Inactive either by migration package or by manual configuration.
Workflow	Invalid label operator [anyLabel]	Occurs when the target Vault does not have Enable label-specific operators in conditional statements for Lifecycle/Workflow feature enabled.	Contact Veeva Support to request feature enablement.
Workflow	GEN-FADDS-II-1023 – value [{field name}] does not resolve to a valid [field]	Occurs when the workflow references a previously shared document field that is no longer shared between document types.	Manually edit the workflow configuration to exclude the document field before deploying the current component.
Tab	GEN-FADDS-ONA-1019 – [standard] sub-components cannot be created	Occurs when migrating custom sub-tabs.	Manually create custom sub-tabs in the target Vault. Reorder tabs as necessary.
Docrelationshiptype	GEN-FREC-ONA-1038 – Modifying [{document relationship type}] is not allowed	Occurs when migrating a document relationship type that references a new document type.	Manually remove the document type reference from the document relationship type. Deploy the current component and manually link the two in the target Vault.
Picklist	GEN-FREC-ONA-1017 – Component is in-use	Occurs when a picklist entry is being used in the target Vault but does not exist in the source Vault.	Manually edit the picklist configuration to remove references to the picklist entry.
Doclifecycle	GEN-FREC-ONA-1017 – Component is in-use	Occurs when a document lifecycle state is being used in the target Vault but does not exist in the source Vault.	Manually edit the document lifecycle configuration to remove references to the lifecycle state.
Objectlifecycle	GEN-FREC-II-1007 – Component already exists with attribute [{workflow name}]	Occurs because the workflow referenced in an entry action is Inactive in the target Vault.	Manually activate the referenced workflow in the target Vault before deploying the current component.