You’re offline. This is a read only version of the page.
Hello everyone,
I'm working on a requirement where a customer needs dynamic functionality in Dynamics CRM 2016 (version 8.2). The goal is to hide options within one option set based on selections made in another option set. Here’s a breakdown:
We have two option sets:
"new_department" with options:
1 = 100001
2 = 100002
3 = 100003
"new_case" with options:
a = 100001
b = 100002
c = 100003
d = 100004
When a user selects option "1" in "new_department", specific options in "new_case" should be visible or hidden. For example, choosing "1" should display options "b" and "d" in "new_case", while hiding options "a" and "c".
The challenge is to implement this dynamically without resorting to hard-coding, as the customer prefers using the description field for defining visibility rules. However, I believe using the description field might complicate maintenance.
My initial thought is to use a "configuration" entity that defines these visibility rules. This entity would list combinations of "new_department" selections and the corresponding visible options in "new_case". While this approach avoids direct coding, it does require creating additional entities and fields.
I'm seeking advice from the community on similar implementations or alternative approaches that are feasible within Dynamics CRM 2016 (version 8.2). We currently don't have access to newer features but are looking forward to leveraging them soon.
Any suggestions or insights would be greatly appreciated!
Share
Report
All responses (
Answers (
96
