web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Customer Insights Fails To Match On Clear Matches

(1) ShareShare
ReportReport
Posted on by 21

Hello everyone.

I'm using Customer Insights to match data over multiple data sets and finding some matching rules working intermittently.

The rules that have issues are of the form Full Name + Date of Birth + Postcode.

Entries are the same data types and set to the correct field type in both data sets.

The values are considered a match when joining or using UNION on those three columns using SQL in the source database.

The same values do form a match with the same rule when deduplicating in a single entity. We add un-matched records on to the primary record source and subsequent matching runs take them back out again at the deduplication phase.

The matching rule does not fail for all records (approximately 10% fail to match from a data set of around 500 rows) but does appear to consistently fail for specific sets of values.

I've tried various combinations of options within the Normalize drop down with no impact.

There's nothing visibly different about the combinations that don't match. I've checked for hidden characters, line breaks, non breaking spaces etc.

Any suggestion on further steps I can perform to either resolve the issue or identify the cause?

I have the same question (0)
  • Scott Stabbert Profile Picture
    Microsoft Employee on at

    Hi Barney,

    I've seen this several times, and each time it was that the strings were indeed different.  ASCII variations, spaces, etc...
    I see you tried those and various combinations.  Would love to see get a data sample and we could test, or take a look at your instance.

    Thanks,


  • Badge Profile Picture
    30 on at

    Hi, If you are using Power Query for the data source, you could add an additional expression column which concatenates the 3 columns together. That would simplify the matching rules and also allow you to view the combined data when records don't match.

  • Suggested answer
    Barney Lawrence Profile Picture
    21 on at
    We managed to resolve the issue in the end.
     
    There was some form of corruption in the definition of the rules that were failing. I suspect this was created when the source data changed and updated the data sets with revised column names before we caught the issue and changed them back again.
     
    The solution was to delete those rules and add them again in the exact same format. While the rules were visibly the same at the front end the new versions began to provide the matches we were expecting.
     
     
    Barney

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Hamza H Profile Picture

Hamza H 140 Super User 2026 Season 1

#2
Nagaraju_Matta Profile Picture

Nagaraju_Matta 128

#3
Abhilash Warrier Profile Picture

Abhilash Warrier 70 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans