This commit is contained in:
2021-08-13 19:36:37 +00:00
parent 26f6ee84b9
commit 1008b506f5

View File

@@ -25,7 +25,10 @@ Aug
Installer
Seeder / evaluation system worked out fully and implemented
Manual pages docs
Extensions to replace current add-on's (accounting etc)
Extensions to replace current add-on's
QBOI
QBI
(if pt, well after release if ever)
Load testing
Beta testing
Rockfish / Back end infrastructure (round robin license fetching / mirror license domains / machines)
@@ -520,15 +523,10 @@ todo:2 many biz objects are not using new PUT methodology
########################################################################################################################
CURRENTLY DOING: Import workorders v8 migrate
CURRENTLY DOING: odds and ends of migrate
todo: sb able to copy the url from help about in v8 ui and use for migrate easily, just copy and paste so it should handle the api v8 shit at end of it
todo: set SEED numbers after migrate to highest wo number as they are not advanced when migrate happens so will be dupes
maybe best to track this in the plugin itself, just increment the highest wo number counter then set it at the end
as the process is not necessarily in order by wo number
todo: task group not migrating, should as it's a v8 feature, also there's a case about it 3438 dropping description field for tg
todo: head office customers link from menu exists but is not implemented, should show customers list filtered by that head office
Inventory handling ideas:
maybe do use inventory, but start out with crazy high numbers for each part
@@ -537,24 +535,15 @@ Inventory handling ideas:
at end of export fixup inventory to balance with v7
this way part requests that are open make sense and workorders still consume inventory properly
todo: calculations at server are off from v7 to v8
for example sample data workorder 40 has labor totalling 145.36 for herb arlens in v7 and 145.35 in v8 for same line due to 3 digits used in calculation causing a round down
(the tax internal value is 8.925 in v8 and 8.93 in v7 due to bankers rounding)
so the likely solution is to apply bankers rounding to the calcs, however there maybe implications when it comes to things like crypto values etc
so need to determine carefully
net = decimal.Round(quantity * price, 2, MidpointRounding.AwayFromZero);
issues: v7 used "Bankers rounding" which is round up if midway so some totals in v8 will be lower than the v7 source record by 1cent.
v8 doesn't yet use bankers rounding but will soon to match v7
"Distance" field in v7 woitemtravel is not exposed in v8 but is actually there, I just missed putting the control on the form
Inventory
I have some more work to do with inventory, for now to facilitate migrate it just puts 1 billion in stock for every part migrated
I will keep the 1 billion bit and be adding code to do a final inventory adjustment at the end of the migrate to bring the v8 balances
into agreement with the v7 balances. (some tricky work needed there due to the vast differences in how inventory works so leaving that for now)
If useinventory is off in v7 it will just ignore all inventory, if it's on it will create an opening balance of 1billion for each part and deduct from each part as it migrates workorders
part requests do not migrate the purchase order id link if there was one in v7; not sure how I'm going to handle this, i was hoping to leave out importing po's but I might just have to anyway
ultimately I can fix up the inventory balance at the end no matter what gets imported, it's just that v8 takes all inventory affecting things very seriously so it's going to
leave a lot of artifacts in the db if it has to adjust and add and remove tons of stuff which I was hoping to avoid. Will have to give it a think.
Inventory
I have some more work to do with inventory, for now to facilitate migrate it just puts 1 billion in stock for every part migrated
I will keep the 1 billion bit and be adding code to do a final inventory adjustment at the end of the migrate to bring the v8 balances
into agreement with the v7 balances. (some tricky work needed there due to the vast differences in how inventory works so leaving that for now)
If useinventory is off in v7 it will just ignore all inventory, if it's on it will create an opening balance of 1billion for each part and deduct from each part as it migrates workorders
part requests do not migrate the purchase order id link if there was one in v7; not sure how I'm going to handle this, i was hoping to leave out importing po's but I might just have to anyway
ultimately I can fix up the inventory balance at the end no matter what gets imported, it's just that v8 takes all inventory affecting things very seriously so it's going to
leave a lot of artifacts in the db if it has to adjust and add and remove tons of stuff which I was hoping to avoid. Will have to give it a think.
============================
@@ -873,3 +862,10 @@ BUILD CHANGES OF NOTE
BUILD 119
- Fixed TLS / SSL issue preventing connecting v8 migrate to our test server via https url
- Fixed money rounding issue on work/quote/pm *order calculations to match v7
- Seed number for next work order after migration now properly set
- Migrate utility server "url" label change to server "address" in label
- Migrate utility now parses out the part it needs from the user entered server url and re-constructs it into a valid url
this means the user can just copy and paste the v8 url they are testing with from the browser address bar and paste into the v8 migrate and it will work