This commit is contained in:
@@ -96,14 +96,22 @@ todo: DataList view and filter are combined and this is wrong
|
||||
filter:[{column:"PartPartNumber",items:[{op: "=",value: "400735"}]}]
|
||||
}
|
||||
|
||||
# METAVIEW
|
||||
This is intended to override the filter at client but it was in conjunction with existing filter which is problematic
|
||||
# METAVIEW / VARIANT
|
||||
NOTES: Metaview is used for two different thigns currently:
|
||||
STATICALLY restricting a list to an always required filter like adm-users and cust-users and cust-customer-notes
|
||||
solution is use variant system like picklist
|
||||
DYNAMICALLY restricting a list to an on the fly filter like ShowAll
|
||||
solution is solved by above changes and can provide alterantive filter programmatically any time
|
||||
|
||||
todo: remove metaview entirely at both ends
|
||||
new system above has one filter and it's replaced by the old metaview so will this be ok or will it be an issue because something already written needs both?
|
||||
probably not but check
|
||||
|
||||
todo: Modify DataList and implement Variant system just like picklists already does
|
||||
must work with same capabilities shown in the current UnitPickList GetVariantCriteria which will work for the current STATICALLY filtered lists
|
||||
(any list where the metaview was static and not optional but required for the view to work)
|
||||
|
||||
|
||||
SEEDER
|
||||
sample datalist is whack now
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user