Can you lock a list collector or make it read only after one of the options is selected

[Cupcake]

I wanted to know if it is possible to make a list collector RO or lock it after a specific value is selected.

So if someone selects the N/A value, I don't want them to be able to select anything else, but if they change their minds and they un-select that value then the list collector should no longer be locked or RO.

Is this even possible?

Thanks,

Karen

[Chuck Tomasi]

Hi Karen,

If you only want one value, this sounds like a better use case for a reference field rather than a list collector. Where is this list collector being presented? Is it on a catalog item or from a related list? Sorry, you image was helpful, but didn't give the full context.

[Cupcake]

Good morning Chuck,

        It is being presented on a catalog item (customer facing). And they want a list collector so the customer can select more than one option.

Thanks,

Karen

[Chuck Tomasi]

Thanks Karen. I'm a bit confused on this part of the requirement though...

So if someone selects the N/A value, I don't want them to be able to select anything else, but if they change their minds and they un-select that value then the list collector should no longer be locked or RO.

If the field is read-only after they select N/A and then they change their mind, how are they going to unselect N/A if it's read-only?

[Chuck Tomasi · Accepted solution]

It would seem like a separate variable is needed here to indicate an N/A value. If they check the box, then a UI policy makes the list collector appear and they can start populating values. That way you have a way to keep the list collector unavailable in the N/A case, but still allow them to choose values when it is applicable. Make sense? two fields - one checkbox, and one list collector, and a catalog UI policy based on the checkbox value to make the list collector appear when needed.