List Control Deselect does not clear e.datasubmitted variable

[ssmoore1]

Hi Everyone,

If you have a list control that has multiple selections, you can clear the selections by creating a button with the javascript below:

var lObj = {dialog.object}.getControl('listcontrol');
lObj._deselectAll();

However, if you do an Ajax call back the e.datasubmitted.listcontrol value which contains the keys of selected rows is not cleared. So lets say 10 rows are selected and the user deselects them. A subsequent AJAX call back even when the list is showing as none selected will have the 10 key values.

How to clear the e.datasubmitted.listcontrol value?

Alpha has figured this out, if you manually deselect each row the e.datasubmitted value is updated appropriately.

Thanks,

Scott

[Davidk]

Re: List Control Deselect does not clear e.datasubmitted variable

Confirmed... the list object properties get cleared, but not e.datasubmitted. Hope you don't mind... I sent off the info to Alpha since I had something else as well.

Confirmed by Alpha as an issue. The workaround is to do this after the ._deselectAll()

{dialog.Object}.setValue('listname',false);

where false means do not fire the change event.

[RichCPT]

Re: List Control Deselect does not clear e.datasubmitted variable

I think you need to 3 parameters, if you want to set the flag that turns off firing of the change event.

{dialog.Object}.setValue('listname',false,false);

[Davidk]

Re: List Control Deselect does not clear e.datasubmitted variable

Did you try it? This is a List control... so... it's a bit different. Actually... looking at this further, this is no onChange event for a List control. If you find something in the List control is firing without the 3rd parameter, please post back. I can't see anything firing.

[RichCPT]

Re: List Control Deselect does not clear e.datasubmitted variable

David, no I had not tested what I wrote in post # 3. But now I have and here's a UX that demonstrates the difference between including that 3rd parameter to the {dialog.Object}.setValue() function:

https://drive.google.com/file/d/0BzF...ew?usp=sharing

Make selections in the LIST using Ctrl-Click and notice the edit box below the list gets updated with the key values of selected items and the 3 edit boxes below get colored green if "C01", "C02" or "P01" are selected. Use the two buttons outlined in red to test with and without using the 3rd parameters to "setValue()".

[Davidk]

Re: List Control Deselect does not clear e.datasubmitted variable

Rich, I think we're talking about different things. Your 2 buttons both have 3 parameters... one button with true for the 3rd param, one with false.

I was saying that you don't need the 3rd param in this case. You only need to pass 2 parameters.

This... will clear the List.

{dialog.Object}.setValue('LIST1',false);

And thanks for the sample.

[RichCPT]

Re: List Control Deselect does not clear e.datasubmitted variable

I know, I was confusing the issue by writing both calls to setValue with a 3rd parameter of false or true. But, omitting the parameter is the same as including it with the value true!

The reason I made a post here anyway is because what was written in post # 2 above:

{dialog.Object}.setValue('listname',false);
where false means do not fire the change event.

I was just trying to say that the second parameter in that function call is not what tells the system to not fire a change event. (In LISTS the event is actually, confusingly, called "onSelect"). I was trying to say if you really didn't want the change/onSelect event to fire then it requires a 3rd parameter to that function and it should be set to false.

I wasn't trying to say the change event "should be" circumvented in this situation. I was just saying if that is what you wanted to do then you'd have to supply a third parameter to that function call.

My demo component shows a case where calling setValue on a LIST must be allowed to fire the change/onSelect event so other fields can be updated on the UX.

[Davidk]

Re: List Control Deselect does not clear e.datasubmitted variable

Right... understood. This works as well...

{dialog.Object}.setValue('LIST1',false,false);

Clear and don't fire List onSelect

[RichCPT]

Re: List Control Deselect does not clear e.datasubmitted variable

Note:

If the LIST has a character key instead of a numeric key then the second parameter to setValue should be an empty string if you are trying to clear the selections from the list.

{dialog.Object}.setValue('LIST1','');

[Davidk]

Re: List Control Deselect does not clear e.datasubmitted variable

Are you saying that with a character key {dialog.Object}.setValue('LIST1',false,false); does not clear the selections? Your example List has a character key.

[RichCPT]

Re: List Control Deselect does not clear e.datasubmitted variable

right. But just so we don't confuse future readers, let me go back to talking about "{dialog.Object}.setValue('LIST1',false);". In my app the second parameter cannot be false when trying to clear the selections from the list. It doesn't matter if the third parameter is included or not or if it's false or true; when the second parameter is false the list will not clear its selections. The second parameter, for my demo list, must be an empty string when trying to clear the list selections because the LIST's return field is of type character.

[Davidk]

Re: List Control Deselect does not clear e.datasubmitted variable

That's why I was asking. With your example UX, with the List return field (ID) being a type of character, "{dialog.Object}.setValue('LIST1',false);" clears the List. It also allows the onSelect to fire. "{dialog.Object}.setValue('LIST1',false,false);" clears the List and suppresses onSelect.

[RichCPT]

Re: List Control Deselect does not clear e.datasubmitted variable

There is a difference in behavior between Version 12.3 Build 2689 and the last official release of 12.3 Build 2999. I was using 2689 and the second parameter has to be '' to clear the list in my example, presumably because of the character ID field. In build 2999 the second parameter can be false or '' to clear the list!

[Davidk]

Re: List Control Deselect does not clear e.datasubmitted variable

Ok... now it makes sense. I had a feeling it was going to come down to an out-of-date release issue because I'd tested this in the last official release, and several of the pre-releases. Good to know.