Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I've a list box on dashboard which having dates as weekly wise and turned ON the "Always One Selected" Property at designer level. It is automatically turning OFF after reload the data and as a workaround using the below -
Setting --> Document Properties --> Trigger --> Document Event Triggers --> on Open --> Add Actions --> Add --> Select in Field --> Selected the value for the field. Save the document, exit doc, reopen and then field automatically selected even after data reload.
By default it will select one value, however the users can select more-than one value from list box and we have requirement should NOT select more than one value (also should not clear the filter).
Is any option can we add the logic at script level to make explicit "Always One Selected" value turned ON in addition to the designer level property setting and appreciate your support.
Thanks in advance!!!
I suspect it may be related to the following, or something similar, hopefully this in addition to what Miguel wrote will provide the full explanation:
"Firstly, it is strongly recommended never to combine "Always One selected" with "Locked Field", not in the least for this very reason. Secondly, it is more difficult to detect conflicts in the client-server scenario than in the desktop scenario and this is why the behavior differs between the desktop and a client and the conflict resolve method is more often activated in the latter scenario. The actual conflict resolve method means that if there is a conflict between the two; "always one selected" will always have precedence over "locked field" since it's an object property affecting the state whereas "locked field" is merely a high level layout operation."
I was able to find this in a defect case that seemed pretty close to what you were describing, but I have a feeling you may be doing something different than locked field that is causing the confusion in things.
Regards,
Brett