OrderBy Bound Value

23 views
Skip to first unread message

Steve Burrows

unread,
Nov 24, 2025, 10:13:35 AM11/24/25
to Migrated By Firefly
In a Browse onl UIController I have a NumberColumn populated by BindValue.
It is calculated and displayed in the grid correctly.

When I use the built in Column Sort or specify the Column as the only OrderBy, the view changes to show 0 or a very few records.

It is not used in any Relations or Where clause.
To keep it as simple as possible, even when I bind my Column value to a hard coded "BindValue(() => 1)" the same happens.

Is there something I am missing ?

Noam Honig

unread,
Nov 24, 2025, 12:04:54 PM11/24/25
to Steve Burrows, Migrated By Firefly
Steve - my guess is that the order by "thinks" that its unique - make sure that the order by is set as non unique

Noam Honig  
Founder & CEO


--
You received this message because you are subscribed to the Google Groups "Migrated By Firefly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to migrated-by-fir...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/migrated-by-firefly/6989b8cd-1023-447d-9e23-0982e541604en%40googlegroups.com.

Steve Burrows

unread,
Nov 27, 2025, 5:22:25 AM11/27/25
to Migrated By Firefly
Thanks, checked that is all Non-Unique. Often shows NO rows in the view.

Have found some code that causes it, and it does seem to be a bug somewhere in Env or more likely FF

With this line of code there is the issue: 
Where.Add(WO.QtyStored.IsEqualTo(WO.CurQty));
Replace it with this and it works :
Where.Add("{0} = {1}", WO.QtyStored, WO.CurQty);

Both fields have the same Type in the Entity and in SQL.

The Profiler shows me the generated SQL is correct and identical except for an irrelevant brackets set of extra brakets in the working version

Ludo Kosters

unread,
Nov 28, 2025, 3:01:34 AM11/28/25
to Migrated By Firefly

Steve Burrows

unread,
Nov 28, 2025, 4:10:40 AM11/28/25
to Migrated By Firefly
Thanks Ludo, that does indeed seem likelly to be the same root bug with the same workaround.

BTW - Its not a simple column ordering issue, I tried A.IsEqualTo(B) and B.IsEqualTo(A)
Reply all
Reply to author
Forward
0 new messages