Upon using the Ad-hoc Download feature in Veeva Network's Configuration Export functionality, a user notices that some specific Data Model fields are not included in the export file. Why are these fields not included in the newly created export?
This behavior is working as designed. When creating the export, the selected configuration may be pointing to specific Data Model fields. Dependencies are automatically added to your selections when creating the export file, however this excludes dependencies for Data Model fields. Since Data Model fields are not automatically added, the user has to be sure that any custom fields which are relevant and required for the selected configuration records are also selected upon creating the export.
Veeva Network Online Help: Creating configuration packages to export
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.