Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Accounts/ManagingAccountInfo/Decoupled_Data_Change_Requests.htm

## Decoupled Data Change Requests

To edit account data that must be validated or verified by a data steward, Vault CRM customers can use native [Data Change Request](../../Integration/Network_Integration/Data_Change_Requests/Data_Change_Requests_Overview.htm) functionality on the account\_\_v, address\_\_v, and child\_account\_\_v objects. This feature is available independent of a Veeva Network subscription (decoupled). However, for organizations without a Veeva Network subscription, admins must separately configure processes for decoupled DCR review, approval, and integration into Vault CRM and other systems.

If an HCP moves to a new office, a user can submit a DCR to change the address on his account. An admin approves the request according to the organization’s address change process, and updates the HCP’s address using an external software system integrated with Vault CRM.

**Who can use this feature?**

* End Users — Browser, iPad, Windows
* [Editing Account Information with Decoupled DCRs](#Editing)
* Users do not require an additional license

### Configuring Decoupled Data Changes for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)
Business Admin Users](#)

To configure this feature:

1. Ensure [Configuring Accounts](../AcctConfig.htm) and [Configuring Data Change Requests](../../Integration/Network_Integration/Configuration/DCR_Configuration.htm) are complete.
2. Grant users the following permissions:

   | Object | Object Permission | Object Type | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | data\_change\_request\_\_v | CRE | * account\_\_v * address\_\_v * child\_account\_\_v | n/a | n/a |
   | data\_change\_request\_line\_\_v | CRE | all | n/a | n/a |
   | dcr\_field\_type\_\_v | CRE | n/a | n/a | n/a |
   | network\_settings\_\_v | R | n/a | All fields | Read |
3. For DCR users, remove Create access from the following objects:
   * account\_\_v
   * address\_\_v
   * child\_account\_\_v

   Do not remove Create access to these objects if the user is also configured to use [CRM Managed Account Types](../../Integration/Network_Integration/UsingNetwork/EnablingbyAcctType.htm).
4. Enable the **data\_change\_request\_mode\_\_v** Veeva Setting with a value of 1.
5. Verify the **network\_customer\_master\_mode\_\_v** Network Setting is 0, which is the default value.
6. Create or activate existing VMOC records for the following objects:

* data\_change\_request\_\_v
* data\_change\_request\_line\_\_v
* dcr\_field\_type\_\_v

When DCRs are created independently of Veeva Network, they are created with the status Submitted. How these DCRs are reviewed, approved, and flow into Vault CRM and other systems must be separately configured based on your organizational master data processes.

#### Enabling Lifecycles on Data Change Requests

Admins can enable lifecycles on Decoupled Data Change Requests, providing workflow control beyond the limitations of standard DCR statuses of Submitted, Pending, and Processed. Enabling an object-specific lifecycle for DCRs allows for the definition of custom states for the approval process.

Enabling lifecycles is not recommended for DCRs managed by Veeva Network.

For details on configuring object lifecycles and enabling them for specific objects, see [Configuring Object Lifecycle States](https://platform.veevavault.help/en/gr/30683/).

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)
End Users](#)

To enable this feature:

1. Ensure [Account configuration](../AcctConfig.htm) and [Configuring Data Change Requests](../../Integration/Network_Integration/Configuration/DCR_Configuration.htm) are complete.
2. Grant users the following permissions:

   | Object | Object Permission | Object Type | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | network\_settings\_\_v | R | n/a | All fields | Read |
3. Verify the **network\_customer\_master\_mode\_\_v** Network Setting is 0, which is the default value.

When DCRs are created independently of Veeva Network, they are created with the status Submitted. How these DCRs are reviewed, approved, and flow into Vault CRM and other systems must be separately configured based on your organizational master data processes.

### Editing Account Information with Decoupled DCRs as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)
End Users](#)

Users edit account information with decoupled DCRs using the same interface as they would for regular DCRs, although admins must process the request separately.

To edit account information using decoupled DCRs:

1. Select the **Edit** action on the appropriate Account Detail page.
2. Edit the desired fields. The lock icon indicates which fields are DCR controlled.

   An object must have at least one field with a type of either DCR (dcr\_\_v) or DCR required (dcr\_required\_\_v) for DCRs to work properly.
3. Select **Save**.
4. Enter any applicable **Notes** describing the reason for the DCR.
5. Select **Submit**.

The DCR status is automatically set to Submitted. For decoupled DCRs, admins must configure separate processes for reviewing, approving, and updating records with the suggested change.

For more information on using DCRs, see [Edit Account DCR (iPad)](../../Integration/Network_Integration/Data_Change_Requests/iPad_DCR_Process.htm#Edit) or [Edit Account DCR (Browser)](../../Integration/Network_Integration/Data_Change_Requests/Online_DCR_Process.htm#Edit).

Support for multi-country users does not apply to Decoupled DCRs.

### Related Topics

[Data Change Requests Overview](../../Integration/Network_Integration/Data_Change_Requests/Data_Change_Requests_Overview.htm)

[Data Change Request Configuration](../../Integration/Network_Integration/Configuration/DCR_Configuration.htm)

[Network and Data Change Request Settings Overview](../../Integration/Network_Integration/Configuration/DataChangeRequestSettings.htm)