What is the best practice for implementing Data Change Requests for team A, but allowing standard functionality (No DCRs) for Team B?
I have received this request now twice from an enterprise customer.
The first scenario we implemented for a multi-country org where countries were distinguished by profiles. Since we wanted to avoid customization, this implementation was difficult and not user friendly. For example, for Canada, we created profile specific custom settings to enable DCR functionality and for a UK profiles that were not leveraging DCR, we created custom settings to enable standard functionality.
Aside from massive data reconciliation concerns, sometimes clients just keep pushing :), our largest UI problem was the edit problem. Typically, we override the standard edit button with the DCR edit button. This DCR enabled users to scroll down the account page, and click edit on an Address record via the related list and they are navigated to the DCR Edit address page. We had to remove the override or else UK users would be taken to the Edit DCR page when clicking edit on an Account. Overall, a lot of training and terrible user experience.
The 2nd request was to distinguish by team. Team 1 and Team 2 sit on the same Commercial profile, functionality is separated by permission sets. For this implementation, we are considering using a validation rule on DCR Line that evaluates the user who is submitting a DCR, and looks at their permission set assignment (see Custom Permissions in SFDC). This seems to be a cleaner approach; however, users who are not to be submitting DCRs, validations in place to prevent, are still able to create New account/addres/child account DCRs. This is a problem for the business.
Any different approaches out there?
Why does the Profile field on DCR Field Type not provide any functionality??
Please sign in to leave a comment.