From 62f79baf2f41a0feb4ca6cd97233aa5174eee2a4 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Sat, 16 Oct 2021 19:06:57 +0000 Subject: [PATCH] upped the tax % number size allowed --- ayanova/devdocs/todo.txt | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index df812981..f74355f6 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -82,7 +82,10 @@ function ayGroupByTag(reportDataArray, tagContains) { } - +todo: tax code too large a value just server error, no message + numeric field overflow + sb either handle larger values or screen them and truncate or just return validation error + what is a sane maximum value?? Update front / back / dotnet 6 is out https://dotnet.microsoft.com/download/dotnet/6.0 @@ -122,10 +125,9 @@ todo: profile the server during seeding, it's unbelievably slow, what exactly is todo: should some things that were tagified be reverted back like in v7 due to reporting and other issues? - todo: tax code too large a value just server error, no message - numeric field overflow - sb either handle larger values or screen them and truncate or just return validation error - what is a sane maximum value?? + + + todo: admin-history page showing http://localhost:8080/adm-history LT:Global but other things are properly translated TODO: 2021-10-15 15:03:10.9008|ERROR|AyaNova.Biz.TranslationBiz|********* GetSubsetAsync problem: Duplicate keys: UnitModelName @@ -884,3 +886,4 @@ BUILD 135 CHANGES OF NOTE - fixed issue with v8Migrate bombing when import tag is set to empty - case 4002 fixed by changing to exporting individual inventory adjustments. Documented in v8 changes from v7 and migration docs. - known bug: v8 inventory is incorrect currently because it synchronizes v7 and v8 to match at the end however it shouldn't for any parts on v7 workorders not set to Used in service as those should be consumed in v8. Working out a solution. +- fixed issue with 8000% tax code failing due to overflow, was defined as a column DECIMAL(8,5) before which meant total 8 digits with 5 to the right of decimal point so max value of 999.99999%, changed to DECIMAL(10,5) to allow as much as 5 digits to the left of decimal point i.e. 99999.99999%