This commit is contained in:
@@ -27,8 +27,7 @@ Users can select a datalistview for a picklist DataList which will in turn affec
|
||||
Users will get the default hard coded DataListView built into the DataList that is specified for that picklist unless it's changed to an alternative datalistview
|
||||
There is a default PickList format and a default DataTable format pre-defined and hard coded at the server with each dataList definition object
|
||||
|
||||
If the client isn't using a particular dataListView it MUST send the DataListView json as one of the following:
|
||||
{default:"PickList"} or {default:"DataTable"}
|
||||
If the client isn't using a particular dataListView it MUST send the ListView json as empty string or omit it entirely.
|
||||
This will instruct the server to use the pre-defined format instead
|
||||
|
||||
JSON DataListView format:
|
||||
@@ -47,6 +46,10 @@ Example:
|
||||
DataListView JSON:
|
||||
[{key:"COLUMN UNIQUE KEY ID",sort:"-" or "+",filter:{any:true/false,items:[{FILTER OBJECT SEE BELOW}]} }, {key:"second column unique key"},{...etc...}]
|
||||
|
||||
Sort property definition
|
||||
ID VS NAME
|
||||
if it's an name *and* id field
|
||||
|
||||
Filter object definition:
|
||||
Has an "any" boolean property which if true means make an OR query of the conditions if more than one, if nore present or false it means AND each condition (if more than one)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user