Baucore

Filter Matching Records Based on Record Type

Taskadmin

By default, Baucore’s duplicate-detection (“Possible Projects” and “Open Projects of Participants,” shown in the Project Check flow and the BC Project Match component) considers every Project and Project Lead a rep could plausibly be creating a duplicate of — regardless of record type. On orgs running several record types side by side (for example, separate types for new-build vs. renovation projects), that can surface matches a rep would never actually confuse with the one they’re creating.

What the setting does

When Filter matching records based on Record Type is enabled, the projectCheck component only returns candidates whose record type matches the record type of the one being created. Everything else about matching — name similarity, geolocation radius, participant overlap — works the same; this setting only narrows the candidate pool before those signals are scored.

Enable it

  1. Go to Baucore Setup → Project Creation.
  2. Turn on Filter matching records based on Record Type.
  3. No further mapping is required — the filter compares the new record’s record type directly against candidate Projects/Project Leads.

This is a global toggle, not per–record type. If your org only uses a single record type for Projects, leave this off — it has no effect and adds an unnecessary comparison.

Still need help?

Our support team is happy to help with anything not covered here.

Contact support