Hi @CRMSarah,
I I think I found the best solution for you - there were a few that I reviewed. As you know, deleting a warning doesn't guarantee it won't come back if someone views or updates the record again. One option, of course, is to make your scenario more rigid so that these won't qualify. I don't think that's an option here since you're reaching out.
You will have to break your existing scenario into two independent scenarios. Both scenarios will be using dual filters. Article section that explains Dual Filters. "Separate filters can be created to specify which new/updated records should be matched with which existing records."
In the first scenario, we're going to filter on the new/updated records with aclient ID field that equals null. After enabling Dual Filters (by checking "Enable Dual Filters"), you will have two filter sections. The first section, called "New DupeBlocker Scenario Filter," filters on inserted/updated records. We will not be putting anything in the existing records filter which is called "New DupeBlocker Scenario Target Filter."
In the second scenario, it will be exactly the same except for the dual filter criteria. Under "New DupeBlocker Scenario Filter," you're going to add a condition that only looks at records that have a Client ID. In the "New DupeBlocker Scenario Filter," you're going to condition on records that have a blank client ID (equals null).
These two scenarios will generate warnings unless both records have a Client ID:
| Scenario | Inserted/Updated Record | Existing Record | Outcome |
| 1 | No Client ID | No Client ID | Duplicate Warning |
| 2 | No Client ID | Has Client ID | Duplicate Warning |
| 3 | Has Client ID | No Client ID | Duplicate Warning |
| 4 | Has Client ID | Has Client ID | Nothing |
I hope this helps!
Regards,
Hi @CRMSarah,
I I think I found the best solution for you - there were a few that I reviewed. As you know, deleting a warning doesn't guarantee it won't come back if someone views or updates the record again. One option, of course, is to make your scenario more rigid so that these won't qualify. I don't think that's an option here since you're reaching out.
You will have to break your existing scenario into two independent scenarios. Both scenarios will be using dual filters. Article section that explains Dual Filters. "Separate filters can be created to specify which new/updated records should be matched with which existing records."
In the first scenario, we're going to filter on the new/updated records with aclient ID field that equals null. After enabling Dual Filters (by checking "Enable Dual Filters"), you will have two filter sections. The first section, called "New DupeBlocker Scenario Filter," filters on inserted/updated records. We will not be putting anything in the existing records filter which is called "New DupeBlocker Scenario Target Filter."
In the second scenario, it will be exactly the same except for the dual filter criteria. Under "New DupeBlocker Scenario Filter," you're going to add a condition that only looks at records that have a Client ID. In the "New DupeBlocker Scenario Filter," you're going to condition on records that have a blank client ID (equals null).
These two scenarios will generate warnings unless both records have a Client ID:
| Scenario | Inserted/Updated Record | Existing Record | Outcome |
| 1 | No Client ID | No Client ID | Duplicate Warning |
| 2 | No Client ID | Has Client ID | Duplicate Warning |
| 3 | Has Client ID | No Client ID | Duplicate Warning |
| 4 | Has Client ID | Has Client ID | Nothing |
I hope this helps!
Regards,
