Records are dowloaded from OpenData, modified, and a Data Change Requests (DCRs) is initiated in a customer Network instance or a CRM Org. Why are the DCR tasks not reaching the corresponding OpenData Master instance for Master Review but are staying as Pending local approval?
This behavior occurs in the following example when newly sent DCRs do not flow to the OpenData instance.
Example: For testing purposes, an Instance Type is set to Sandbox, instead of Normal for a Network instance. If a Network instance is in Sandbox Mode, the submitted DCRs do not go to the Master instance.
To have the Instance Type set to Normal instead of Sandbox, open a ticket with Veeva Support.
The described behavior can also be caused by a misconfiguration of the Data Source. When defining a new System under System Interfaces in Network, the Proprietary option is enabled (checked). This option allows the user to specify whether the source system contains proprietary data, which (if set) is never forwarded to Veeva OpenData as an Add or Change Request.
The behavior can also occur if there is a field that needs to be approved by local data stewards. Under Data Model > Customer Master > select object > review the fields that are included in the impacted Data Change Request (DCR).
In the Change Procedure section, it is defined how changes to the field value are handled:
Accept - Changes to this field are accepted automatically.
- Review - Changes to this field are always forwarded for local data steward review. This setting overrides the auto-approve workflow setting, if it's set.
- Default - Change behavior is defined by the global workflow settings (for example, if the workflow setting is set to Auto-Approve for an object, then changes to this field are auto-approved; otherwise, changes are routed to local data stewards).
Veeva Network Online Help: Add a Data Source