Announcements
New fields enabled by default
To support enhancements in version 26R2.0, four new fields will be added and enabled by default.
Fields that are enabled by default can impact your current configurations. Evaluate any potential impact before 26R2.0 is released to your Sandbox and Production Network MDM instance.
Fields for unmerged records
The following system fields have been added to HCO, HCP and custom main objects to provide additional details on unmerged records.
| Field Name | Label | Description |
|---|---|---|
| record_unmerged_date__v | Unmerged Date | Date when the record was unmerged. |
| record_unmerged_from_vid__v | Unmerged from Network ID | Network ID of record that this record was unmerged from |
| record_unmerged_original_vids__v | Unmerged 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. |
Supported countries
-
All countries
| Additional 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. |
For information about the enhancement, see the New fields for unmerged records topic.
New field for OpenData 2.0
Support for License sub-objects is being added in this release. Licenses now also include a separate component for Identifier data (for example, NPI numbers in the US and Tax IDs in Europe).
A new field will be added to the License object and enabled by default to define a License record as either a "License" or an "Identifier".
| Field Name | Field Label | Field Type | Description |
|---|---|---|---|
| object_cat_type__v | Object Category Type | Reference Type |
This is an important field that determines if the record is a License or an Identifier. Possible values: LICENSE, ID or no value (for existing Licenses). The default value for new records is LICENSE. |
Supported countries
All countries/regions except the following:
-
Belarus
-
Burkina Faso
-
China
-
Ethiopia
-
Hong Kong
-
Iraq
-
Japan
-
Macao
-
Madagascar
-
Mali
-
Sierra Leone
- Russia
-
Tajikistan
-
Turkmenistan
-
Uzbekistan
-
ZZ (All Other Countries)
| Additional Field Details | |
|---|---|
| Managed by OpenData? | Yes |
| Enabled by default? |
Yes, for all Network MDM instances. |
| Immediate data impact? | Yes |
| Profile layouts |
The field will be added to the GlobalStandard layout for HCPs and HCOs. It must be added to custom profile layouts. No impact or action required to custom layouts if you do not use the OpenData 2.0 data model or the Identifier for Licenses. |
For information about the enhancement, see the OpenData 2.0 data model topic.
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.
-
Reporting – Queries or saved reports using SELECT * will return different results.
Action required to prepare for these fields
Before the fields are added in this release, the following tasks should be considered:
-
Audit Downstream Systems - Identify target exports that pull "all fields" and either update downstream systems to accept the new data or limit the subscription to specific fields only.
-
Review Custom Reports - Update any SELECT * reporting queries to use explicit field names instead, if those reports don't require these fields.
-
Plan Configuration Updates - Add tasks to your 26R2.0 release checklist to update custom profile layouts if you plan to use this data.