This commit is contained in:
@@ -11,11 +11,31 @@ LISTVIEW REPLACE CURRENT <----HERE not THERE ---v
|
||||
(below this is all past for reference)
|
||||
FILTER
|
||||
Very similar to columnview in that it's saved at the server then triggers a refresh and server handles from local copy
|
||||
Client needs to send current local time and date to server with list request so it can apply relative date filters
|
||||
Server accepts request clientnow,listview,filterid and applies any relative filter calcs in sqlWhere generator at server
|
||||
/*
|
||||
OLD EXAMPLE:
|
||||
{"offset":0,"limit":10,"dataListKey":"CustomerDataList",
|
||||
"listView":"[
|
||||
{\"fld\":\"customername\",\"sort\":\"+\",\"filter\":{\"items\":[{\"op\":\"=\",\"value\":\"dfdfdf\"},{\"op\":\"=\",\"value\":\"3333\"}],\"any\":true}},
|
||||
{\"fld\":\"customerphone1\",\"filter\":{\"items\":[{\"op\":\">\",\"value\":\"44444\"},
|
||||
{\"op\":\"<\",\"value\":\"7777\"}]}},
|
||||
{\"fld\":\"customeremail\"}
|
||||
{\"fld\":\"customerheadoffice\"},
|
||||
{\"fld\":\"customertags\",\"sort\":\"+\"}]"}
|
||||
|
||||
NEW:
|
||||
columns:["PartInventoryTransactionEntryDate","PartPartNumber","PartWarehouseName","PartInventoryTransactionQuantity","PartInventoryTransactionDescription","PartInventoryTransactionSource","PartInventoryBalance"]
|
||||
sortBy:[{"PartInventoryTransactionEntryDate":"-"}],//All sorted columns here as keyvalue pairs value is a string of "+" for ascending "-" for descending and are IN ORDER of how to be sorted
|
||||
filter:[{column:"PartPartNumber",any:true/false,items:[{op: "=",value: "400735"}]}],
|
||||
clientCriteria:"2" //could be anything here that makes sense to the list, in this case an example customer id for customernotedatalist
|
||||
|
||||
columns are represented in a higher level object DataListTableOptions
|
||||
sort and filter are in here
|
||||
|
||||
columns and sort are a singleton per datalistkey,userid persisted automatically (no alternative "views" just one of these). User can set them or reset them to default.
|
||||
filter is different: user can persist a filter by name for future selection, sharing with others (public). The default filter is no filter.
|
||||
*/
|
||||
TODO (round 1):
|
||||
SERVER
|
||||
DataListSqlFilterCriteriaBuilder - modify to handle date tokens using client timestamp (old filter code already put back in comment form)
|
||||
|
||||
CLIENT
|
||||
Implement filter UI to construct local filter object that is temporary and stored in session state
|
||||
doesn't have to do anything specific yet, just handles the filtering into an object for the next stage
|
||||
@@ -25,6 +45,9 @@ LISTVIEW REPLACE CURRENT <----HERE not THERE ---v
|
||||
Need filter drop down to select which columns to filter which triggers opening regular filter items
|
||||
Needs also to show a filter beside "headings" which are filtered so it's known
|
||||
Or maybe if it's not too ugly filter on each one, nahh theres no room I think
|
||||
|
||||
SERVER
|
||||
DataListSqlFilterCriteriaBuilder - modify to handle date tokens using client timestamp (old filter code already put back in comment form)
|
||||
|
||||
TODO (round 2):
|
||||
Send to server (as unsaved filter, not dealing with saving just yet) with datalist request and get back filtered data
|
||||
|
||||
Reference in New Issue
Block a user