I have a requirement for a custom field on Account that will have a drop-down with values that are dependent on the user. This was already "implemented" prior to me getting here and it wasn't done in a way that I would ever do. The current implementation has three custom option set fields, one that everyone sees and 2 that are user specific. Processes were created to hide the general field and other user specific field and only show the field specific to the user. This solution has problems and I want to scrap it considering I now need to add 1 more specific user and a group of 6 users that all need the same dropdown options. Ideally I would like to create a single field on Account where the drop-down is dependent on a role or some other field on the user and not specific users. I am new to Dynamics with some Salesforce experience and many years working with Siebel. I found some different ways of implementing drop-downs dependent on other drop-downs using code or lookups. I'm really just looking for the best approach not a step by step how to implement it.
1. What would be the best option on the user record? Role, custom field?
2. What is the best approach to dynamically filter the options on the Account custom field based on the user's role/custom field?
Sounds like you came up with a good supported solution :)
Thanks for the suggestion. I may end up doing something like that for another requirement where I need to constrain a dropdown based on the account owner. I did already go a different direction with this one. I created a new entity that stores the dropdown values and another numeric value that I need to bring to the Account when the value is selected. On the account I created a lookup field to the new entity and a calculated field to grab the numeric value. The way I constrained the lookup was using Access Teams and assigning the users to the access team of the records they need to see in their dropdown.
To avoid a spiderweb of relationships and lookup fields, I would probably go with custom JavaScript on the form and using the SDK to query the user's security role(s).
Sometimes it's a hard balance between supported, OOB solutions and small, clean, custom solutions.
André Arnaud de Cal...
292,160
Super User 2025 Season 1
Martin Dráb
230,962
Most Valuable Professional
nmaenpaa
101,156