test mega data

ayanova/devdocs/todo.txt

@@ -19,24 +19,32 @@
 
 
 
-
-	Report designer improvements
-		add group by method to standard functions and document
-			ayGroupBy
-		settle on a standard for naming for preparedata parameter, update docs to match	
-			it should reflect that it's a combination or package of different things one of them being the report data	
-		remove default sample helper, css from new reports template
-		change new reports template to be simplified and stardardized
-		Clean up docs to properly explain what comes into preparedata and which keys are which 
-			in docs it says see below or something but that's not ideal, put it directly into both sections if necessary in a code markdown block
+APOLOGIZES the previous email was sent before I finished:
 
 
+Have completed the migrate using 133:
+
+Case 4002 still has issues
+- adjustments where serials were added via v7 are now CORRECTLY accounted for in v8 yayyyy but...
+ - adjustments where serials were removed via v7 adjustment STILL do not appear to be accounted for in v8  (It looks like you have coded IF the serials were ADDED through a v7 adjustment, but doesn't look like coded for instances where REMOVED via a v7 Adjustment)
+- serial selected in a v7 "open" workorder still showing as available serial with the Part in v8 - see my suggestion about this that the enduser themselves adjust because is
 
-	See 3999 append about unit model name/number
 	case 4002 - I  will check after performing import that serials match, BUT see my note as there may be an issue with serials that in v7 "are not consumed" because the workorder is "open" but in v8 would and should be considered "consumed"
 
+Case 3999
+- see my possible suggestion.....
+
+
+I have not made a case, but there is a noticeable lag when moving to different datalists..... what sort of time lag would be expected when a datalist has (for example) 10768 workorder records?
+i.e. 4073 customers for the Customers datalist <- a count of 4 seconds
+i.e. 10768 workorders for the Work Orders datalist <- a count of 5 seconds
+(when I next go to the datalist during that same "up" time for the server, even whenlogged in as another user, almost instantaneous which i believe is expected because then already cached)
+
+
+
 	security jwt tokens and expiration, can a user just keep working if they are set to inactive because their token hasn't expired?
 		should tokens refresh periodically and have a super short life?
+		https://stackoverflow.blog/2021/10/06/best-practices-for-authentication-and-authorization-for-rest-apis/?utm_source=Iterable&utm_medium=email&utm_campaign=the_overflow_newsletter
 
 	Update front / back / dotnet 6 is out
 		https://dotnet.microsoft.com/download/dotnet/6.0