Hi, firstly, thank you for this it's a great tool. One question - does a user need any particular rights for this to work? I've deployed it and it works perfectly for me, but it doesn't launch or work on the form when other users with lower security profiles save records.


JLattimer wrote Apr 5, 2014 at 3:07 AM

It doesn't do any magic - it executes the SDK duplicate check - using the same duplicate detection rules. So with that said I'd double check to make sure the lower security roles have read access to the Duplicate Detection Rule entity on the Core Records tab for starters. There may be other permissions required - honestly I haven't dug into that part enough to see what the minimum permissions are. Otherwise if you are On Premise you could turn on tracing and check the logs to see if you can catch which permission is missing otherwise you could maybe use Fiddler or the browser's debugging tools to look at the network traffic to look for any failed requests to see if the error gives an indication.

indiadhaval wrote Feb 24, 2015 at 11:17 PM

We were facing the same issue. As suggested, after assigning READ access to the Duplicate Detection Rule entity on the Core Records for the Security Role in question resolved the issue. It works for all the users who are assigned that Security Role now. It works perfectly without any issues.

wrote Feb 24, 2015 at 11:18 PM