Administrators can create rules to transform field values in the APIs and in export files for downstream systems. You can also use transformation rules to override OpenData values before records are pushed to Veeva CRM.
Example use cases:
Remove specific address types from Veeva CRM, for example, mailing addresses.
Display only the Ownership Hierarchy in Veeva CRM (remove the noise of relationships for reps in CRM).
Set fields (for example, Specialty or Medical Degree) with no value to a custom value.
postal_code__vfield to only five digits for US addresses.
Hide OpenData addresses in Veeva CRM if they have an ordinal greater than 10.
Change all corporate names to uppercase characters.
Override OpenData's retired HCP status based on a target flag.
Note: Transformation rules can be applied to locally managed records and records managed by OpenData and third-party data providers.
This feature is on by default in your Network instance.
Retain original data in Network but transform the data output for your downstream system.
Each system can have its view of the data. Rules are assigned to specific systems, so you can customize data for different systems.
Flexible integrations with Veeva CRM and other downstream systems. Using transformation rules reduces the need to create customizations for other systems.
Network API support. Data can also be transformed using transformation queries in target subscriptions, but transformation queries are not supported for API requests.
Define a rule or set of rules for a specific source system. Rules are created using Network Expressions for a specific object and field.
Apply the rules to target subscriptions or the API.
Run the job to transform the data and then export it to the downstream system.
Veeva CRM integration
Use transformation rules to customize the data that is pushed to CRM.
By applying transformation rules on target subscriptions and to the integration user, the rules can then be applied when data is pushed to Veeva CRM.
This includes the following processes in CRM:
Network Account Search
DCR Inbound Process
Network Bridge subscription
Filtering child account and address records pushed to Veeva CRM
Leveraging transformation rules, you can identify the addresses and parent affiliations that should be set to Inactive Veeva CRM. CRM functionality can then remove these Inactive records so they do not display in CRM.
To ensure that Mailing type addresses are not pushed to CRM, create a NEX rule that changes the status of all mailing addresses to Inactive. Then, the CRM settings will delete those inactive addresses so they do not display on accounts in CRM.
To do this, use the following CRM settings and values:
FILTER_INACTIVE_NETWORK_RECORDS_VOD - Set to 1
NETWORK_ADDRESS_DELETION_PROCESS_VOD - Set to 2
For detailed information about the settings, see Handling Inactive Network Records in the Veeva CRM Online Help.
If a transformation rule is applied to filter specific values from CRM, for example, remove mailing addresses or display the ownership hierarchy, then it is recommended to remove those values from being selected by users in CRM.
If you are filtering out mailing addresses, ensure that Mail Only addresses cannot be selected by users in the picklists.
If you are filtering to only display the Ownership hierarchy (Ownership,Affiliation), ensure that Claims relationship types cannot be selected.
Network Bridge updates
After transformation rules are applied to the target subscription, run a Network Bridge job to ensure CRM is in sync.
Update all records - Run a full Bridge job. In the Network Bridge configuration, set the Revision Data Value setting to 0 to update all records.
Update affected records - If you know the records that need to be updated in CRM, add the Veeva IDs (HCP/HCO) to the Export by VID option in the target subscription. When the next Bridge job runs, it updates those records.
For example, if you know which HCPs records contain Mail Only addresses, add those VIDs to the Export by VID job so your next Bridge job removes those addresses.
Create a rule
To add a transformation rule:
In the Admin console, click System Interfaces > Transformation Rules. Click New Rule.
Type a Name and Description.
Names cannot contain spaces.
Select a System. All rules are associated to a specific source system.
The system cannot be changed after the rule is saved.
Tip: If you make a mistake, you can clone the rule and change the system.
Veeva CRM considerations
If this rule will be used to transform data before it is exported to CRM, ensure that the following settings are applied:
System - Define the system for CRM.
Target subscription - Choose the subscription used for CRM.
API - Choose your CRM integration user.
In the NEX Rules section, add the rules.
For each NEX rule, define the following:
Object - All objects (except custom keys) are supported.
Field - The field. The list is filtered for the selected object.
Code Description - Define a meaningful description. This description will also display in associated target subscriptions.
NEX Rule - Type the Network Expression for transforming the data. The NEX function must return a value for the transformed data.
Expand the field if you need additional space. Click Verify to validate the NEX syntax. A message displays at the top of the page to indicate the validation status.
See a list of examples in the Example rules section below. For help with creating network expressions, see the NEX functions and NEX operators topics in the Veeva Network Online Help.
To create another rule for this system, click Add Rule.
Tip: Use the Handle icon to reorder the rules if the sequence of the rules matters. For example, you can chain together several rules to transform data for a specific field.
After a NEX rule is created, it can be enabled, disabled, or deleted. If a rule is not enabled, it will not be applied to the target subscription/API.
Apply to Target Subscriptions - Associate the rules to target subscriptions. Choose one of the following options:
All Target Subscriptions that match the system - Apply these rules to any target subscription that uses the source system.
Specific Target Subscriptions - Choose the specific target subscriptions that these rules apply to. All the enabled target subscriptions that use this source system display in the list.
Apply to Search and Retrieve API - Apply the transformation rule on the API for a specific user.
Active users that have API access display in the list.
Save the rule.
The NEX rule functions are validated. If there are issues, an error displays.
All rules in your Network instance display on the Transformation Rules page (System Interfaces).
On the target subscription configuration, the Transformation Rules section displays any rules that have been applied to the subscription.
Note: When the job runs, transformation rules are applied before transformation queries.
The following details display:
Object, Field, Description
Transformation Rule - Click the link to open the rule configuration.
View Rule - Click to see the NEX rule. This is the current rule (from the Transformation Rules configuration page).
After you save a subscription configuration, the transformation rules display in the Data Flow View.
Target subscription job details
After the job runs, you can view the rules on the Job Details page.
The following details display in the Transformation Rules section:
Object, Field, Description
NEX Rule - The code as it existed when the job ran so you can understand the customizations that were made to the exported data if the NEX rule has since changed.
Transformation Rule - The current name of the rule on the Transformation Rule configuration page. Click the name to open the configuration page. If the rule has since been deleted, the original rule name displays with a (Deleted) comment beside the name.
Job error log
If there is an issue with the NEX rule, errors will be logged. The job will fail in some cases; for example, if the NEX rule references a lookup table that does not exist in your Network instance.
After a transformation rule is saved, it can be cloned. This is helpful if you want to apply the same or similar rules to another source system.
When a rule is cloned, only the description and the NEX rules are copied to the new rule. You can create a name, select the source system, and apply the rules to target subscriptions or the API.
Transformation rules can be applied to Retrieve and Search API requests.
Search API - Supported requests
Search API + supplemental
Retrieve API - Supported requests
Retrieve Child Entity
Batch Retrieve Entity
Batch Retrieve Child Entity
Retrieve Change Request (IncludeEntity = True)
Batch Retrieve Change Request (IncludeEntity = True)
During this Retrieve HCP request, the transformation rule sets the Mail Only address record status to Inactive.
Support for fields with null values
In the Network API, if a field is empty, the record is not returned in the JSON. For transformation rules, the field is returned in the response entity JSON because the transformation rule adds a value.
specialty_1__v field value is NULL, so it is not returned in the Retrieve HCP response. A transformation rule runs that changes the NULL value to "UNSPECIFIED__c". Now, the Specialty field will be returned in the JSON: "specialty_1__v":"UNSPECIFIED__c".
Hashtags reflect the untransformed values. They do not change for transformed values.
If you search using hashtags, the results returned are based on the original value of the data.
Example transformation rules
|Deactivate mailing addresses
|if(addres_type__v =='M', 'I',address_status__v)
|Limit US zip codes to 5 digits
|if(country__v == 'US', left(postal_code__v,5),postal_code__v)
|Deactivate relationship types that are not Ownership or Affiliation
|if(not(relationship_type__v in ['2','7356','12']), 'I', parent_hco_status__v)
|Override retired HCP status
|if(hcp_status__v == 'R' && status_override__c == 'Y', 'A', hcp_status__v)
|When Specialty is null, then set it to a custom reference type
|if(ISNULL(specialty_1__v), 'UNSPECIFIED__c', specialty_1__v)
|When Medical Degree is null, then set it to a custom reference type (UNSPECIFIED__c)
|if(ISNULL(medical_degree_1__v), 'UNSPECIFIED__c', medical_degree_1__v)
|Set record type
Note that this uses a lookup table.
|LOOKUP('type_mapping__t', 'record_type', hcp_type: hcp_type__v)
Note: For rules that change an object status to inactive (for example, addresses or relationships), if it is pushed to Veeva CRM, some CRM settings will then remove those records. For more information, see the Veeva CRM integrations section above.