This commit is contained in:
@@ -1,13 +1,30 @@
|
||||
LIST / GRAPH FILTERING SORTING AND COLUMN RETURNED
|
||||
|
||||
DataListView objects are used to filter and sort and determine display order and presence of columns returned by:
|
||||
DATALIST
|
||||
A dataList is a raw source of data for returning to client
|
||||
All below is based on a datalist which is a predefined list of fields, rights and some query info for joins etc
|
||||
There are specific datalists made for picklists, viewing all grid data, KPI shit, whatever is required during development
|
||||
DataLists are hard coded, only a DataListView can be customized to limit, filter, sort what is returned from a pre-defined DataList
|
||||
DataLists have roles associated with them, only a user of one of those roles can fetch that list (or see it as an option when doing reporting etc)
|
||||
|
||||
DATALISTVIEW
|
||||
A DataListView is a filtered, sorted, reduced version of a DataList
|
||||
It can be saved and set to private or public
|
||||
They can be made on the fly in the Client and don't need to be saved as the Client will always send the datalistview json string with the request
|
||||
DataListView objects are used to filter and sort and determine display order and presence of columns in order to feed these client needs:
|
||||
DataTables (was grids in v7)
|
||||
Reports
|
||||
Select boxes (on forms like selecting a part or a client)
|
||||
Select boxes PickLists (on forms like selecting a part or a client)
|
||||
|
||||
When the DataList route is hit it's used to get all of the above types of data.
|
||||
A dataListView JSON string is sent with the request in order to have the server sort/filter/return
|
||||
|
||||
PICKLISTS
|
||||
Picklists are based on a particular DataList with rights for ANYONE
|
||||
Client will be hard coded to specifiy the exact dataLIst
|
||||
Users can select a datalistview for a picklist DataList which will in turn affect how it appears and what's returned
|
||||
- This is like the PartDisplayFormat feature of v7 only for everything!
|
||||
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:
|
||||
@@ -43,7 +60,7 @@ AUTHORIZATION:
|
||||
We provide a DataList suitable for picklists with ANY role access and anything with sensitive info has it's DataList Required roles to higher level
|
||||
This way can still supply for picklists but hide sensitive infor for tables etc
|
||||
Rights to DataListView follow rights to underlying object and also rights to make a datalistview itself
|
||||
|
||||
|
||||
Filter operators:
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user