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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / When Matching Records ...
Customer experience | Sales, Customer Insights,...
Answered

When Matching Records When Would You Use the Include All Feature?

(0) ShareShare
ReportReport
Posted on by nicseitz 40

Working on a current POC and at the matching phase. 

I noticed an include all records selection. The info button states the below:

"If you include all records, every record in the entity will be a unique customer and matched to every following entity."

I assumed the matching process would match records between entities based off of primary key and subsequent keys defined in earlier process.

Can anyone explain this feature to me, please?

I have the same question (0)
  • Verified answer
    John Wiese Profile Picture
    John Wiese Microsoft Employee on at

    Matching works off of the order provide of the entities used for unification as well as the rules you setup.  So if you have entities A, B and C you setup the order you want to match them.  Typically you will want to choose the entity with the most accurate, and most filled in data as your first one.  For simplicity here let's assume you set them up in the order A, B, C and that you setup a simple Email match between A and B, and also B and C.  What happens is that we will match the A nd B entities on the email rule you setup.  Once we have the matches we then will match those against C using the email rule you setup.

    So now consider the "Include all records" checkbox.  What does this do?  Well, let's say you checked that on the B entity.  What happens then is we match A and B using your email rule.  The result will be all the records from A & B that matched, and all the records from B that did not match.  The records from A that did not match B will not be brought forward since we didn't check the "include all records" on the A entity.  

    Basically think of it as a way to include all the records in the unified profile even if they don't match another entity.  If you only want the unified profiles to contain records that exist in one of the prior entities in the list then you would not check the box.

    Hope this makes sense.  

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 189 Super User 2026 Season 1

#2
CU11031447-0 Profile Picture

CU11031447-0 100

#3
NeerajPawar Profile Picture

NeerajPawar 66

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans