Duplicate management in Winter 15

  • 3
  • Question
  • Updated 12 months ago
  • Answered
How can we allow users to quickly enter leads and contacts through Skuid tables but still take advantage of the duplicate management feature that's GA in Winter 15?
Photo of Joe Ort

Joe Ort

  • 2,256 Points 2k badge 2x thumb

Posted 4 years ago

  • 3
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,006 Points 20k badge 2x thumb
Official Response
Ok here is a field report.   Duplicate Management and Skuid - the current situation. 

I implemented Duplicate Management in a Dev Org. 

I turned on a Matching Rule that fired if a record's email matched that of another record. 
Then I started playing with a series of combinations of Duplicate Rules to see what the impact was on the skuid pages.

 


1. When the Action option is "Block" for Create or Edit, the "Alert Text" gets posted at the top of the page where you are trying to save, and the user is prevented from saving. 




2. When the Action is Allow and only the report operation is triggered, the page successfully saves and the duplicate record set entry is created

3. When the Action is Allow the alert operation is triggered - there is no alert shown.  The user is just taken to the Lead Detail page. 


So two out of three.. Not bad,  but we can do better. 


The other aspect to duplicate management is the duplicate record set - a group of records that are all duplicate one to another. This allows reporting and custom fields etc.  Skuid cannot currently connect to the duplicate record set in a model because of the API level we are currently using.  We will be fixing this API level in our next release and this will allow more complete reporting on duplicate records.  I believe this will also allow us to successfully replicate option 3.

Stay tuned for continued improvements.  We'd love to hear any of you who are being successful with duplicate management as it currently is possible with Skuid.