boxfoot
/ getDependentPicklists.cls (2017 approach)
Last active
October 1, 2024 17:55
Handle cases where one dependent option can be used for multiple controlling options
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /* | |
| * Apex doesn't expose dependent picklist info directly, but it's possible to expose. | |
| * Approach: | |
| * * Schema.PicklistEntry doesn't expose validFor tokens, but they are there, and can be accessed by serializing to JSON | |
| * (and then for convenience, deserializing back into an Apex POJO) | |
| * * validFor tokens are converted from base64 representations (e.g. gAAA) to binary (100000000000000000000) | |
| * each character corresponds to 6 bits, determined by normal base64 encoding rules. | |
| * * The binary bits correspond to controlling values that are active - e.g. in the example above, this dependent option | |
| * is available for the first controlling field only. | |
| * |