Comments
I second this. And specifically OnRecordSelect. This event does not work if the Power Apps Grid Control has Editable set to "No". I heard someone actually opened a bug for this which is why it's now disabled. That is ridiculous if true. Example: we have a custom search for Contacts. The results are presented in a subgrid. When you select a Contact record it automatically shows that Client's Cases in a second subgrid. Read only grid should only mean you can't make inline edits. You should not disable events. To keep this working MS has provided us with a query string parameter to eneable onRecordSelect. But, I would love to get rid of this redirect hack.
In real-world use, duplicate detection cannot account for scenarios like nicknames vs. legal names (e.g., “Blanche” vs. “Bunny”), so duplicates still occur. If Blance Moses is in our system and she interacts online using her nickname of Bunny Moses duplicate detection can't compare "Bunny" to the nickname field already in the system under Blance's record. Someone who doesn't know her will inadvertantly create a new record for her.This makes it especially important that the merge process fully resolves duplicates in a single step rather than leaving inactive records behind.