ayanova/devdocs/todo.txt

@@ -109,7 +109,8 @@ todo:1 workorders - need to set billing and service address from customers on mi
 
 ## CLIENT MISC ITEMS
 
-- 1 Can't mass delete work orders, jobs log says not authorized?
+- 1 Distance field missing from workorder travel section, is defined at server, just not put on to forms
+- 1 workorderitemexpense list has column named "summary" twice but one is notes column, something fishy there
 
 -3 case 3864 Joyce misc item - Layout improvement:
 	Summary (workorder overall) - looks like now can enter unlimited amount of text..... BUT if only using for four or five words, its still showing ALL this blank space across the entire screen
@@ -315,6 +316,11 @@ todo:2 remove widget now? Back and front (comment out obvs not remove entirely)
 
 ## SERVER MISC ITEMS
 
+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
 
 todo: clean up / simplify bizroles.cs at server for large objects like work order with same for all children (see quote for how it's done)
 
@@ -524,7 +530,11 @@ 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
 
 
 ============================
@@ -866,7 +876,30 @@ BUILD 118
 	existing menu item in workorderitemloan edit form is available to see all workorder items this loaner was selected on
 - v8 migrate 
 	Made the v7-import tag an optional field users can set to anything or nothing (still want to keep the ability because many users may find it useful to be able to know which objects were imported or for mass deletion)
-	Workorder export implemented
+	Custom fields now properly migrate their customized names from v7 to v8 and display properly on forms
+	Custom fields time values now properly migrate with the correct time (was not set to UTC before so was out by variance from GMT/UTC)
+	Workorder export fully implemented and probably riddled with bugs
+		Problems I know about already
+			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.
+		Problems I don't know about
+			It would be helpful and most efficient to test migrate against as wide a variety of db's as possible before I port the migrate code from workorder over to quotes and PM's as well
+			I'm deliberately holding off on quotes and PM's until we've had a chance to test it and shake out the most obvious bugs to save time later
+			so if you have any db's to test against now's the time, the weirder and more fucked up the better.  They need to be current version of AyaNova though to work with the plugin.
+			The plan is ultimately that it should just handle any db with weird data without the user having to "fix" or change anything in v7 before it will migrate.
+			Please put any new issues found into testing cases individually, if there is an error include the full export log with error from the migrate form which can be copied and pasted into the case
+
+
+