ayanova/devdocs/todo.txt

@@ -16,12 +16,12 @@ LISTVIEW REPLACE CURRENT <----HERE not THERE ---v
 			Fix error: "enumSelectionList" is not defined on the instance but referenced during render
 				prevents enum filtering
 
-			META filters: Test if can set a filter on a column that is also a meta filter column but using a regular column name like for example Usertype on user datalists
-				maybe I can make all the server data criteria columns meta and just duplicate the ones the user sees?
-				Because there is gonig to be an issue with this either way, it probably *should* be set to meta only columns used fixing the following problem as well:
-				
-			META filters: are showing as a filter in the UI but not really there from user perspective
-				Need to not have user see or even think about meta filters
+			META filters: Make sure ALL serverdatacriteria meta columns are key named "meta*" to fix two problems
+				in cases where it's using existnig user facing columns make dupes with meta* names
+
+			META: Return datatable data
+				make sure "meta" columns are not included in filter return list
+				user should never be aware of them at all, some are security related, not that they can do anything but it's just a waste of bandwidth and leaks information
 
 			Not liking the default filter, could lead to confusion
 				User needs an easy way to definitively de-filter completely

ayanova/src/components/data-table-filter-control.vue

@@ -402,6 +402,9 @@ export default {
         this.close({ refresh: true });
       }
     },
+    enumSelectionList: function(enumKey) {
+      return window.$gz.enums.getSelectionList(enumKey);
+    },
     addFilterCondition(editItem) {
       // filter:[{column:"PartPartNumber",any:true/false,items:[{op: "=",value: "400735"}]}],
       let filterItem = { op: null, value: null, display: null };