Timeline for What is the best way of dealing with multi-tier dependent picklists?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11 at 10:05 | vote | accept | compski | ||
| Oct 27, 2022 at 12:02 | comment | added | Adrian Larson♦ |
Well, that was just one small piece of the implementation. You had mentioned lwc, so that is a reasonable fallback for the UI side if need be. But there should not be any permutations/combinations involved. You should just be able to do Tier_1__c != Tier_2__r.Tier_1__c.
|
|
| Oct 27, 2022 at 6:26 | comment | added | compski | @AdrianLarson I tried setting up just 2 custom objects for the first 2 levels (Destination Zone & Province). Loaded in all the unique values in both objects. If I were to setup all the Lookup Filters the filter criteria will be at least 100 criterias long. I'm sorry this suggestion is not at all feasible | |
| Oct 26, 2022 at 0:08 | answer | added | Adrian Larson♦ | timeline score: 4 | |
| Oct 25, 2022 at 17:44 | comment | added | Adrian Larson♦ | Seems like picklists themselves may be a poor fit here. Have you considered lookups to a custom data model? More flexible and should be relatively simple to work with. Lookup filters are OOB too. | |
| Oct 25, 2022 at 17:12 | history | asked | compski | CC BY-SA 4.0 |