From 7488e73d8d4ca26682b65de4902e59f06b072574 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 5 Aug 2021 00:57:09 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 5 +++++ ayanova/src/views/ay-data-list-column-view.vue | 3 ++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index f48f8acc..f7af7660 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -532,6 +532,11 @@ todo MISC: Notification code from workorder/quote/pm *item* grandchildren? Why is this a thing? shouldn't it be removed entirely, it's jsut wasted cpu cycles can a user even subscribe to any of these? Should they? check that jobs don't run during seeding + see if server jobs are staggered (i.e. don't run at the same time) + maybe set the repeat interval off by a small amount so they can't sync up? + or maybe they just run sequentially from the initial trigger anyway? + But even so, staggering the repeat interval will mean less jobs running in the same overall job cycle + ITEMS section of workorder form needs to stand out somehow more, maybe a splash of color in the icon or something profit$ diff --git a/ayanova/src/views/ay-data-list-column-view.vue b/ayanova/src/views/ay-data-list-column-view.vue index 075b18e0..a7c49777 100644 --- a/ayanova/src/views/ay-data-list-column-view.vue +++ b/ayanova/src/views/ay-data-list-column-view.vue @@ -442,7 +442,8 @@ function initWorkingView(vm) { //Pass 1, iterate the columns first for (let i = 0; i < columns.length; i++) { let fld = vm.fieldDefinitions.find(z => z.fieldKey == columns[i]); - +//bugbug: if there is a incorrect field in the view it surfaces here when user attempts to set the column view because it doesn't turn up so fld here will be null +//in this case ideally the fix would be to ignore the probably bogus column and move on to work without it let o = { key: fld.fieldKey, title: null,