Someone reported a few days ago that they were having some issues with findSublistLineWithValue on 2026.1, anyone remembers the exact issue? was it returning

null

instead of

-1

or it was that it returned line numbers as strings?

If you are looking for a checkbox value, be warned it was "T" and it's now true you need to match against. I fixed a Production issue for this fault last week.

That's a small change with massive impact. They shouldn't have done that. I don't even remember if I am using "T" to find the line.

I exclusively use a helper that checks for

true

or

'T'

or

1

from all my search/query results because this happens every so often to me. I also noticed it in a bom query on 2026.1 that used to be true/false and is now T/F

NElliott, was that a global change for all checkboxes or only for findSublistLineWithValue?

FYI, I wrote an POC script and execute it in Client and Server side and I was not able to reproduce this reported behavior in Release Preview running 2026.1 when tested with a Sales Order record.

@Christopher Quackenbush checkboxes in search columns return as T, from a query true. SS1 as T SS2 as true etc etc it's been inconsistent even before 2026.1 The latest change in 2026.1 with checkboxes is using the findSublistLineWithValue to find a set checkbox you now use true as the value to match not T.