What if the user changes his/her mind? Why would you want to disallow this?
Cause it writes to a tracking log. I have an override feature for them to do a correction.
There are probably a few ways to do this. You could run an OnObjectEnter script trigger that exits the field if the field is not empty.
Another way is "HideWhen". Have two of the same field one enterable the other not.
Set the enterable one to hide when the field has data, have the none enterable one to hide when empty.
As you say you have an override set up should the value need changing.
This is a bit confusing.
Do you mean you have a field formatted as a checkbox set and a value list with several values, and you want that once a specific value is checked, that value cannot be unchecked – but other values can be added? (i.e. one can only add to that field, not remove from it?)
Erolst yes that's exactly what i want.
ZoocMan85, how many items in your value list? I only ask because this could be an occasion when a repeating field could be used.
This approach would need a value list for each item placed on individual iterations of the repeat.
A script could trigger on entry, get the repetition number and if it's empty allow entry or if an entry exists exit the field.
There are limitations to this method, more items mean more repetitions but better than many individual fields.
There is probably a clever custom function to do the same but I haven't looked into that.
Sent from my iPad