Hi Isomorphic,
I'm trying to use a ListGrid summary row of a ListGrid with many joins and serverside added security WHERE-clauses with setSummaryRowDataSource(), as the ListGrid is very big and I always want the summary row.
I only need summaries for some fields, so I'm currently playing with outputs:
Here I'd expect that this will affect the fields after SELECT in the SQL, but it also seems to affect WHERE clauses, as now conditions as generated for tablename.null, which obviously can't work (is tablename.fieldname as expected without the outputs). I remember having a similar issue before and will look up the thread (I have a feeling that issue had to do with not-generated joins).
This also is true if you set the outputs clientside with setOutputs().
To me this seems wrong and not matching the description that this is happening. If you agree I can try to create a testcase if needed.
Best regards
Blama
I'm trying to use a ListGrid summary row of a ListGrid with many joins and serverside added security WHERE-clauses with setSummaryRowDataSource(), as the ListGrid is very big and I always want the summary row.
I only need summaries for some fields, so I'm currently playing with outputs:
Specifies, for this operationBinding only, the list of field names that should be returned to the client. Typically this will be a subset of the DataSource.fields, but note that this is not a requirement; outputs can include fields that are not defined in the DataSource's field list. In this case, the server will return extra fields even if DataSource.dropExtraFields is true.
You specify this property as a string containing a comma-separated list of field names (eg, "foo, bar, baz")
You specify this property as a string containing a comma-separated list of field names (eg, "foo, bar, baz")
This also is true if you set the outputs clientside with setOutputs().
To me this seems wrong and not matching the description that this is happening. If you agree I can try to create a testcase if needed.
Best regards
Blama
Comment