Share
Report
3On a custom form clicking on any column header in the header grid to filter produces the error "Column is not
filterable" on every column — including standard bound fields like JournalNum (String), JournalType (Enum), CreatedDate (DateTime), etc.
The line grid on the same form does not have this issue - all columns are filterable.
Observations:
-The view works in table browser, all columns are filterable there.
filterable" on every column — including standard bound fields like JournalNum (String), JournalType (Enum), CreatedDate (DateTime), etc.
The line grid on the same form does not have this issue - all columns are filterable.
Observations:
-The view works in table browser, all columns are filterable there.
- The line grid with a seemingly identical setup works fine
What causes "Column is not filterable" on ALL columns of a cross-company view when used as the form's primary datasource in a TaskParentChild pattern? Is there a known
framework limitation or a specific property/configuration I'm missing?
What causes "Column is not filterable" on ALL columns of a cross-company view when used as the form's primary datasource in a TaskParentChild pattern? Is there a known
framework limitation or a specific property/configuration I'm missing?
Categories:
I have the same question (0)
All responses (
Answers (
