Match and merge FAQs
Review the following frequently asked questions (FAQs) for the match and merge in Network MDM.
General
What is Match and Merge in Veeva Network MDM?
A process to identify potential duplicate records and combine them into a single, accurate record.
What are match rules used for?
They define the criteria that Network MDM uses to identify potential duplicate records.
What are merge outcomes in Network MDM?
The results of the merge process, indicating how data from the duplicate records was combined.
What happens to the data from the records that are merged?
Data is consolidated into a single record based on the defined survivorship rules.
Configuration and logic
What is match configuration?
The setup and settings that control how the matching process is performed in Network MDM.
What are Match Rule Collections and how are they used?
Match Rule Collections are independent sets of match rules and data groups that can be reused across different source subscriptions or API calls. Instead of recreating rules for every new data load, you can group countries with shared requirements into a Country Group within a collection. This allows for centralized management and ensures match configuration remains consistent across various business processes.
Is it possible to match records that have been opted out for data privacy?
By default, opted-out records are excluded from matching to protect privacy. However, administrators can enable Opt Out Matching Settings to include them. If enabled, matches to opted-out records can be automatically rejected or sent to a data steward for review. This prevents the creation of duplicate records for HCPs who have requested to be restricted from processing.
Specialized match features
Can I match data without actually importing it into Network MDM?
Yes, using the Ad Hoc Match feature. This allows you to upload an external file, such as a marketing campaign list, and compare it against your Network MDM instance or the global Veeva OpenData database to find matches. The results, including Network IDs for matched records, are exported back to you without creating or updating any records in your system.
Troubleshooting
Is there a way to troubleshoot issues with the match process?
Yes, Network MDM provides tools and guidelines for troubleshooting why records might not be matching as expected.
Why didn't my records match as expected?
The most common cause is ineffective Data Grouping. Before match rules run, Network MDM separates data into "blocks" or groups based on shared attributes. If two records do not land in at least one identical data group, the system never compares them, and a match can never occur. See Grouping data for more information.
Administration
How do I work with match rules in Network MDM?
Through a dedicated interface where you can create, edit, and manage the matching criteria.
Where can I configure the matching process in Veeva Network MDM?
Within the match configuration settings in the administration section.