ayanova/devdocs/todo.txt

@@ -14,6 +14,9 @@ todo: poitem edit form currency fields when updated by server on save lose curre
 	maybe currency control does not respond to underlying data changes it didn't initiate?
 	seems maybe it's ok in main form but that's maybe just because it doesn't change values automatically
 
+todo: datatable single select mode, is this even a thing?
+	if not then I should remove that code, it's just taking up space and complicating shit for no reason
+
 todo: acc-service-bank is using a decimal control instead of a  currency control for currency field
 todo: Unit override warranty lifetime active should disable or even hide "override length" field
 todo: OverrideLifetime is bad text, fix it, key is "UnitOverrideLifeTime" and maybe it just says "Life time warranty"
@@ -25,7 +28,7 @@ todo: inconsistent use of browser language and browser languages
 	and some are using the entire array
 	In some cases array will work, in others it requires single
 	need to check into this and be consistent or understand what's happening
-	I'm guessing we favor languages as it seems to be accepted by whatever is using it and it will work better if the first one is unsupported
+	I'm guessing I favor languages as it seems to be accepted by whatever is using it and it will work better if the first one is unsupported
 
 todo: locale.js  look into this:
 	  	// also for sake of future proofing and edge cases need to have it be manually settable as well
@@ -85,11 +88,11 @@ todo: actual Customer report with names populated
 		TODO: for reporting this would be more ideal if it populated the displayName fields
                 //I'm doing that in this object already by fluke, and don't really want to populate them always and in other objects but for reporting maybe 
                 //have a report mode get or I guess just do it all here (but then need for export as well, but then again this is the way it gets for export via getreportdata)
-                //so perhaps we have a REPORT format of a biz object model and that format has display names mirroring all the fields
+                //so perhaps I have a REPORT format of a biz object model and that format has display names mirroring all the fields
                 //it's fetching it here anyway, might as well do the whole shebang?
 	So, bottom line might be an alternate ReportModel (e.g. Customer / ReportCustomer) with display fields (not the model sent to the client during normal work as that would eat up bandwidth unnecessarily)
 	Stop thinking about efficiency too much, this is a time to waste a few cycles but make a much easier to work with data return for reports / export
-	All display fields are populated as is done with PO similarly and that is done *in* get report data because that's also the export route use too which fits nicely with what we want
+	All display fields are populated as is done with PO similarly and that is done *in* get report data because that's also the export route use too which fits nicely with what I want
 	Make it work with Customer then backport to all the extant objects and add to item migrate todo list below as a step so it doesn't get missed in future ones
 
 	
@@ -114,7 +117,7 @@ todo: v8 migrate additions
 		message doesn't clearly say that number was exported already
 		is there a way to still export them?
 	Is it possible to login during migrate to the v8 server?
-	Need a running count per item, we have the total at the start so it should show what item it is currently processing of that count like 50/1000 or something
+	Need a running count per item, I have the total at the start so it should show what item it is currently processing of that count like 50/1000 or something
 
 
 
@@ -170,13 +173,9 @@ todo: how to add locale keys in future after release without erasing all data?
 
 
 CURRENTLY DOING: PurchaseOrder - restock required
-todo: if poitem has woitempartrequest (is a part request)
-	quantity can not be any different than the requested amount, that entire line item must be dedicated to the part request which makes 
-	restock reports etc much easier to handle
-	
-todo: on order committed must be taken into account
-	poitem with woitem is entirely for wo
-	does not go into calcs for restock at all, so need to adjust to filter OUT poitem with woitempartrequest values
+
+todo: currently working on datatable to emit full row selections since there is no ID to select items in restocklist as it has no id
+	maybe a materialized view would but I want live data only
 
 todo: restock required feature
 	Next step is to create an extension to copy to existing or new workorder for selected items
@@ -186,7 +185,9 @@ todo: restock required feature
 	not going to do this inside the po itself
 	same process for part requests as well
 
-
+todo: if poitem has woitempartrequest (is a part request)
+	quantity can not be any different than the requested amount, that entire line item must be dedicated to the part request which makes 
+	restock reports etc much easier to handle
 
 
 
@@ -194,7 +195,7 @@ todo: MIGRATE_OUTSTANDING note for part requests feature
 	maybe add UI button etc for it even with no actual list / form or whatever
 todo: can edit po number but if I set an existing po number 4 to 23 for example and the last autogenerated is 22 it will happily make another 23 so there are now two
 	what I want to happen is it skips existing numbers
-	Research this method and how we can work with it and give it a good think because it maybe a dangerous thing to expose or just fuckery
+	Research this method and how I can work with it and give it a good think because it maybe a dangerous thing to expose or just fuckery
 	it really only will be of use in rare circumstances and most likely when importing v7 with oddball numbers (Scott?)
 	not many serialized objects, maybe a utility to do wahtever, renumbering with them could be done for just that purpose entirely
 	(along with resetting the autoid number)
@@ -764,7 +765,7 @@ todo: ONGOING search for memory leaks
 @@@@@@@@@@@@@@@ ROADMAP STAGE 7 - EXTENSIONS (was plugins)
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
-Step 1: get the current active license count for all extensions so we know what we're dealing with here
+Step 1: get the current active license count for all extensions so I know what i'm dealing with here
 Step 2: which extensions in which order and some can be left off entirely?
 
 Plan the order of criticality for extensions
@@ -791,7 +792,7 @@ Plan the order of criticality for extensions
 todo: setup for automated trial testing ability so can just link users
 	Maybe, rather than having seperate servers for testing, have it instead generate a User account on the fly for each user who wants to trial
 	Automatically re-create the data on a cycle of some kind
-	Needs warning message about being a shared instance of AyaNova so be careful what you type and also you may see things other people typed that we have no control over
+	Needs warning message about being a shared instance of AyaNova so be careful what you type and also you may see things other people typed that I have no control over
 
 todo: WINDOWS INSTALLER
 	Runner harness wrapper thing?
@@ -886,7 +887,7 @@ Another payment processor?
 DONATE
 Send a tip / buy a coffee link to the graphic designer who made the rabbit logo 
 	follow the link from the docs appendix open source acknowledgements page
-	if we use it in release we should at least send them the small amount they get tipped
+	if I use it in release I should at least send them the small amount they get tipped
 
 Send a tip / donate to teh favicon generator guy
 	https://realfavicongenerator.net/