ayanova/devdocs/todo.txt

@@ -57,6 +57,8 @@ todo: workorders - need to set billing and service address from customers on mig
 
 todo: custom required rules only apply to new records!!
 
+todo: 
+
 todo: Translation: "Physical" address seems wierd, rename to Street address or Delivery address or Service Address or whatever
 todo: broken rules can't save should color save button red in addition to disabled some forms can't see what's what
 todo: Any "Priority" type value in UI that has colors should use ayaFireAlt icon instead of round circle which is for minor status only
@@ -79,6 +81,13 @@ todo: REPORTING
 	also it should be named to indicate the server is modifying the data before it's sent to the template
 	i.e. name everything so it's clear what is being done where
 
+todo: reporting custom fields
+	Joyce ran into an issue with a custom field defined as currency adn wanted to use it in a calculation on a report but it presents as a string
+	Look into either a helper to ease that or more ideally it presents as the type that it's supposed to be pre-modified? (not sure of the implications)
+	Do I have a custom fields helper already?  What does it do?
+	Maybe translated custom fields alongside the string version??
+	Users see it as currency would be just as confused as Joyce was expecting it to be a number
+
 todo: cleanup unnecessary use of a ayatype access inside the Methods of objects as it's now available in vue via main object, 
 	e.g. where you see this: ayaTypes().XXXX you can replace it directly with this: $ay.ayt().XXXX and then REMOVE completely the ayaTypes() method in the vm of that object
 todo: use const, not let unless need to reassign the variable
@@ -312,7 +321,8 @@ CURRENTLY DOING: labors (but involves contract change below)
 	todo: on put needs to return object if prices updated, not just concurrency token!!
 		prices are *always* updated contract or not bc set by choice of part, not at client
 		any object modified at server must return object
-		only some won't need this
+		only some won't need this, but at the end they may all need it one way or another
+		for efficiency I guess don't return it if no change but keep an eye out
 
 
 	todo: complete the backend contract stuff: it needs to also handle tagged specific values as well