4

So we have been working with one master record type for a long time, where adding values to a picklist at Object level simply made the values appear automatically where that picklist was used.

Recently, we split our records into two record types. Record type A does not use the picklist in question at all, while Record type B has the picklist on it's page.

What the issue is, is that when adding values to the picklist field at Object level, those values don't get added to the actual visible field till you add the values both in the picklist field on the Object and in the Record Type picklist.

This is super-annoying, as we don't have our record types share picklists that we need to change values in based on record types.

I need values that are added to picklists at Object level to appear as available selection choices the moment I add those values.

Is there a way to do this, or are we forever stuck now with a 2-step process to add values to picklists now? (even if that picklist is used on only 1 record type to begin with)

Is there a way to stop the picklist form being controlled by record type?

1 Answer 1

3

As the product stands today, the two-step process is currently required; you can't have picklists that automatically ignore record types. However, there is an idea you'll want to vote on: Show picklist values across all record types.

1

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .