A Data Change Request (DCR) is showing an error message about a missing Parent Affiliation. It is a Change Request generated after matching a customer Add Request with an already existing Veeva OpenData record. The user wants to keep the affiliation from the OpenData record as Active. Why is the user receiving the error message about the missing required field?
On the new Affiliation (Dept of Accident and Emergency Services in the above example), the Parent Affiliation field is set to Rejected" but the Status is modified. This is what is causing the error.
When the user accepts or modifies any fields on an object, the system thinks to create that object and therefore the required fields check gets triggered. In case the user wants to reject the new affiliation, reject all the fields on that object.
There is no need to augment the same values to the existing affiliation. The user can remove all the augmented fields on the existing affiliation. Therefore, the user should proceed with rejecting all fields on the new affiliation and thus process the DCR.
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.