I have a multi-select list on an Item record that is behaving very wrong in my opinion. Wondering if anyone else seeing this.
1. If you display the multiselect list in normal view, you can select and deselect and this will fire appropriate events for field change (which I need). If I refresh the screen without saving, the multiselect returns to its former selections (as expected - I haven't saved any changes prior to refreshing).
2. If you display the multiselect list to be 'shown as list', you can attach and remove, but this is where everything goes wrong:
a) No field change events fire when you attach or remove (I would expect they would since after all this is a multiselect field on the form just being displayed in a nice list format - it's not a sub-list)
b) If I refresh the screen without saving, the multiselect RETAINS the changes I made (similar in behavior to a real sublist - but this is NOT).
This presents two issues:
1. I need to know when the user is adding or removing from the list as part of necessary workflow process to enable/disable other fields on the record. I can't when 'shown as list'
2. If someone removes or attaches and then leaves without saving, the selections remain saved -- very unintuitive and obviously not good.
If I leave in normal view to stop #1 and #2 above, then I have to deal with the common user error of forgetting to hold the shift or control when selecting multiple in the list which is just as bad.
Anyone seeing this? Seems like a couple of defects exist here.
-Steve