Announcements
Advanced notice for new fields
To support a planned enhancement, new system fields will be added and enabled by default in version 26R2.0 (subject to change).
This early notification is provided so you can evaluate any potential impact on your current configurations and activities ahead of time.
-
26R1.1 - The fields are not available.
-
26R2.0 - The fields are currently planned to be in this release, but the release timing is subject to change.
New fields
| Field Name | Label | Description | Object |
|---|---|---|---|
| record_unmerged_date__v | Unmerged Date | Date when the record was unmerged | HCO, HCP, custom objects |
| record_unmerged_from_vid__v | Unmerged from Network ID | Network ID of record that this record was unmerged from | HCO, HCP, custom objects |
| record_unmerged_original_vids__v | Original Record Network IDs | The Network IDs of the records that existed before they were merged. It confirms which original record's data is now being restored into the new record. | HCO, HCP, custom objects |
Supported countries
-
All countries
Field details
| Managed by OpenData? | Yes |
| Enabled by default? |
Yes, for all Network MDM instances. |
| Immediate data impact? | Yes |
| Profile layouts | The fields will be added to standard layouts. They must be added to custom profile layouts. |
Considerations for existing Network MDM instances.
When fields are enabled by default, it can impact target exports and reporting.
-
Target Exports - New fields will automatically be included in target subscriptions configured to export all objects and fields.
To prevent issues, either update downstream systems to accept the new data or limit the subscription to specific fields only.
-
Reporting – Queries or saved reports using SELECT * will return different results.
-
CRM Integrations - The fields must be mapped in your Network Bridge to flow down to Veeva CRM or Vault CRM.