We’ve explained the different types of picklist available in our previous blog. This time, we are going to talk about what are the ways to maintain picklist where its value is represented by ID via API.
Usually, we can create a cross-reference table within the integration process to store the picklist values and their corresponding IDs. We can then retrieve the IDs and the matching values via the cross-reference table when needed. However, this approach may require a technical person to maintain the picklist values and IDs, as a non-technical person may find it difficult to maintain as it requires amending the cross-reference table via the integration process.
Alternatively, we can externalize the picklist cross-reference table within an application instead. For example, when integrating between Netsuite and Salesforce, we can create a picklist cross-reference table in Salesforce to store the picklist values and IDs. When a picklist ID is retrieved from Netsuite, the integration process will be able to retrieve the corresponding values from this table and insert into Salesforce.
With this approach, a non-technical user too can access and maintain the picklist values as well as IDs flexibly.