Data Change Request Configuration
Data Change Requests are petitions to modify certain account data and are created when data is changed and needs to be validated.
To enable Data Change Requests:
- Ensure Configuring Accounts is complete.
- Grant users Edit permission to the Account object.
- Enable the Data Change Request Mode Veeva Setting with a value of 1.
-
Grant access to the following Data_Change_Request_vod record types:
- Account_vod
- Address_vod
- Child_Account_vod
-
Provide Visualforce page access to the user profile for the following pages:
- Edit_Account_DCR_vod
- Edit_Address_DCR_vod
- Edit_Child_Account_DCR_vod
- New_Address_DCR_vod
- New_Child_Account_DCR_vod
- New_Parent_Account_DCR_vod
-
Remove DCR user Create access to the following objects:
- Account
- Address_vod
- Child_Account_vod
Do not remove Create access to these objects if the user is also configured to use CRM Managed Account Types.
-
Override the standard Edit button for the following objects with the following Visualforce pages:
- Edit_Account_DCR_vod for the Account object
- Edit_Address_DCR_vod for the Address_vod object
-
Add the appropriate DCR Controlled Fields to page layouts assigned to users logging DCRs for the following objects:
- Account
- Address_vod
- Child_Account_vod
There are three objects for DCRs:
- Data Change Request Header
- Data Change Request Lines
- DCR Field Type
Data Change Request Header
- Users must have CRU access to the Data Change Request object
- Users must have FLS read permission to fields on the Data Change Request object
- Verify that a VMOC exists for the Data_Change_Request_vod object. If not, create a new active VMOC with a Type of Top Level.
Data Change Request Lines
- Users must have CRU access the Data Change Request Lines object
- Users must have FLS edit permission to fields on the Data Change Request Lines object
- Verify that a VMOC exists for the Data_Change_Request_Line_vod object. If not, create a new active VMOC with a Type of Related to Top Level.
DCR Field Type
- User profile must have R access to the DCR Field Type object
- Users must have FLS read permission to fields on the DCR Field Type object
- Verify that a VMOC exists for the DCR_Field_Type_vod object. If not, create a new active VMOC with a Type of Top Level.
- The user country is defined by the Country field on the DCR Field Type object. The Address Country field should contain the ISO 3166-1 alpha-2 country codes. Multiple codes should be separated by a semicolon (e.g., DE; FR; IT).
Field Label |
Field Name |
Data Type |
Description |
Size |
Required? |
---|---|---|---|---|---|
DCR Field Type ID |
Name |
Auto Number |
DCR field type ID |
|
Yes |
Country |
Country_vod |
Text |
ISO 3166-1 alpha-2 country code. |
255 |
Yes |
Object API Name |
Object_API_Name_vod |
Text |
CRM object API name |
43 |
Yes |
Record Type Name |
Record_Type_vod |
Text |
CRM object record type - this is the untranslated label of the Record Type |
80 |
Yes |
Field API Name |
Field_API_Name_vod |
Text |
CRM field name |
43 |
Yes |
Field Type |
Field_Type_vod |
Picklist |
Indicates field type |
|
Yes |
Unique Key |
Unique_Key_vod |
Text |
Unique key that prevents duplicates. Consists concatenated values of:
|
|
|
For DCR Field Types to work correctly on iPad and Browser, the values in the Name field and the Alpha_2_Code_vod field on the Country_vod record must have the same 2-character ISO 3166-1 country code. The Country_Name_vod field on the record can contain the full name of the country.
Profile and Profile Name are not supported in the DCR Field Type field.
DCR Fields
DCR Header fields
Field Label |
Field Name |
Data Type |
Description |
Size |
Required? |
---|---|---|---|---|---|
|
ID |
ID |
Data Change Request record ID. |
|
Yes |
DCR ID |
Name |
Auto Number |
Data Change Request ID. |
|
Yes |
DCR External ID |
DCR_External_ID_vod |
Text |
External Data Change Request ID. External ID, unique case insensitive. |
100 |
No |
Parent Data Change Request |
Parent_Data_Change_Request_vod |
Lookup(Data Change Request) |
Link to parent DCR. Used only if multiple DCRs are created in a single step. Account DCR is always a parent. Other DCRs linked to it. |
|
No |
Date Time |
DateTime_vod |
DateTime |
Date and time DCR has been submitted. |
|
No |
Sent Datetime |
Sent_Datetime_vod |
DateTime |
Time the record has been sent to Customer Master for approval. |
|
No |
Response Datetime |
Response_Datetime_vod |
DateTime |
Time the processed record has been received from Customer Master. |
|
No |
Mobile Created Datetime |
Mobile_Created_Datetime_vod |
DateTime |
Time the record was created on mobile device. |
|
No |
Mobile ID |
Mobile_ID_vod |
Text |
Field used by mobile products for synchronization. External ID, unique case insensitive. |
100 |
No |
Mobile Last Modified Datetime |
Mobile_Last_Modified_Datetime_vod |
DateTime |
Last time modified on a mobile device |
|
No |
Account |
Account_vod |
Lookup (Account) |
Account that have been modified. |
|
No |
Account External ID |
Account_External_ID_vod |
Text |
Account external ID. External ID, unique case insensitive. |
100 |
No |
Address |
Address_vod |
Lookup (Address) |
Address that have been modified. |
|
No |
Address External ID |
Address_External_ID_vod |
Text |
Address external ID. External ID, unique case insensitive. |
100 |
No |
Child Account |
Child_Account_vod |
Lookup (Child Account) |
Child account that have been modified. |
|
No |
Child Account External ID |
Child_Account_External_ID_vod |
Text |
Child Account External ID. External ID, unique case insensitive. |
100 |
No |
Type |
Type_vod |
Picklist |
Data change request type. |
|
Yes |
Notes |
Notes_vod |
Text Area |
User notes. |
255 |
No |
Status |
Status_vod |
Picklist |
DCR Status. |
|
Yes |
External Status |
External_Status_vod |
Picklist |
DCR status in Customer Master. |
|
No |
Result |
Result_vod |
Picklist |
DCR result returned from Customer Master. |
|
No |
Resolution Note |
Resolution_Note_vod |
Text Area (Long) |
DCR resolution notes returned from Customer Master. |
32 768 |
No |
DCR Line Fields
Field Label |
Field Name |
Data Type |
Description |
Size |
Required? |
---|---|---|---|---|---|
|
ID |
ID |
DCR line ID. |
|
Yes |
DCR Line ID |
Name |
Auto Number |
Data Change Request Line ID |
|
Yes |
Data Change Request |
Data_Change_Request_vod |
Lookup (Data Change Request) |
DCR line belongs to. |
|
Yes |
Mobile Created Datetime |
Mobile_Created_Datetime_vod |
DateTime |
Time the record was created on mobile device. |
|
No |
Mobile ID |
Mobile_ID_vod |
Text |
Field used by mobile products for synchronization. |
100 |
No |
Mobile Last Modified Datetime |
Mobile_Last_Modified_Datetime_vod |
DateTime |
Last time modified on a mobile device |
|
No |
Field Name |
Field_Name_vod |
Text |
Name of modified field. |
40 |
No |
Field API Name |
Field_API_Name_vod |
Text |
Field API name in CRM. |
43 |
Yes |
External Field API Name |
External_Field_API_Name_vod |
Text |
Field API name in Customer Master. |
255 |
No |
Old Value |
Old_Value_vod |
Text Area (Long) |
Old field value. |
4000 |
No |
New Value |
New_Value_vod |
Text Area (Long) |
Field value after user update. |
4000 |
No |
Final Value |
Final_Value_vod |
Text Area (Long) |
Field value after Customer Master validation. |
4000 |
No |
Result |
Result_vod |
Picklist |
Line result returned from Customer Master. |
80 |
No |
Resolution Note |
Resolution_Note_vod |
Text Area (Long) |
Resolution notes returned from Customer Master. |
32 768 |
No |
DCR Support Fields
Type | Size | Supported in DCR |
---|---|---|
Autonumber | 30 | No |
Check box | Yes | |
Currency | Yes | |
Date | Yes | |
DateTime | Yes | |
Yes | ||
Formula | No | |
Geolocation | No | |
Lookup | Yes | |
Master-Detail | Yes | |
Number | Yes | |
Percent | Yes | |
Phone | Yes | |
Picklist | 255 | Yes |
Picklist (Multiselect) | 4000 | No |
Roll-Up Summary | No | |
Text | 255 | Yes |
Text (Encrypted) | 175 | No |
Text Area | 255 | Yes |
Text Area (Long) | 32,768 | No |
Text Area (Rich) | 32,768 | No |
URL | 255 | Yes |