In some cases, CDMS object records may not appear as expected. The following table provides possible causes and solutions for this occurrence.
Learn more about object records in our FAQ.
| Cause |
Solution |
| The object was not registered due to mapping
|
- Open the appropriate YAML, CSV, or other source data file.
- Review the file and check for errors.
| The object was orphaned (i.e., an ancestor didn't exist or an ancestor was not registered due to mapping)
|
- Check the object record status on the Run or Post-Run Summary page.
- If the status is Pending, review the Repaired Objects worksheet in the Migration Report.
| The object was skipped directly, or its parent was skipped
|
- Open the appropriate YAML, CSV, or other source data file.
- Review the file and check for errors.
Records are either skipped explicitly or because they’re descendants of a DNO (Did Not Occur) Event:
- For example, if a Form is mapped correctly and the data appears in the CSV file, review the form’s Event to troubleshoot.
- Check to see if Event creation is being targeted in more than one place.
- Review the YAML files and ensure that no other YAML files are targeting the same event.
Skipped records are not represented on the Run & Post-Run summary page. They can only be found in the Orphaned Task Types worksheet in the Migration Report.
| The object was manually deleted or is missing from the source data
|
Ensure you have the most recent collection of source data.
|
| An error or failure was encountered during the Run or Post-Run steps
|
Failed records can cause descendant records to remain Pending.
Contact your Veeva Services representative for assistance.
|
| The Run or Post-Run steps did not complete
|
Do not attempt to change the Load status and retry the steps as it may compound the problem.
Contact your Veeva Services representative for assistance.
|
| | |