multibox selection always on top

[Anonymous]

Hi,

I can't find a solution to this problem ...

I would like to remove sorting by State in the multibox, exactly like a listbox.

I attach example with two different behaviors.

someone did solve this problem?

thanks,

Ste

[Clever_Anjos]

I don´t see the difference, could you explain better?

[Anonymous]

too concise sorry... i try to explain me better

if you select a date on a list control selected value remain in its original position eg:

01/01/2010

02/01/2010

03/01/2010

04/01/2010

if you select a date on a multibox control selected value it's always on top, breaking the origina order eg:

02/01/2010

01/01/2010

03/01/2010

04/01/2010

i try to change sort order (State, expression, original, none) but with no results.

[Clever_Anjos]

Well.. The listbox is getting on top here... Am I missing something?

[Anonymous]

Hi Stefano,

I guess that there is no way to have exactly the same behaviour.

But if you want to select a date and you wish to see only following dates,

you can enter the expression in your multibox.

=if (len(GetFieldSelections(TempDate))>0,if (TempDate >= GetFieldSelections(TempDate),TempDate), TempDate)

You will only see dates which are after your seletcd date! But maybe this works for you and

your customer!

Hope this helps!

Regards

[#6]

Looks like a "feature". You are supposed to manipulate that using the "State" sort option.

If you unclick that, it should be sorted like the listbox.

I think you need to contact Support and report a bug.

Cheers

[Anonymous]

[Anonymous]

Expression:

= if (len(GetFieldSelections(TempDate))>0,if (TempDate >= GetFieldSelections(TempDate),TempDate), TempDate)

[Anonymous]

the problem is the order visualization and not the content filter, because i need also to select the dates before the selection.

I'm building a date From->To selection control based on multibox.

I think this is a bug...

thanks all

[Anonymous · Accepted solution]

FYI friom QV support

"Dear Stefano,

Thank you for providing the sample QVW, I want to confirm that this is a bug and it has been filed with bug ID 6177.

The good news is that this bug has been fixed and it is going to be included in the next release (SR6). I have done some testings within an internal release of SR6 and it works."