ayanova/devdocs/todo.txt

@@ -45,47 +45,14 @@ CURRENT ROADMAP
 CURRENT TODOs
 =-=-=-=-=-=-=
 
+TODO: Widget edit form, new record sb time and dates pre-filled in? Server involved? How to handle new record initial date set?
+	- Seeing a few issues that are probably related to having an empty record on start of new object
+	- Don't start blank basically
+	- some objects may be configurable what the default date/time range is so maybe enable that for widget to test
+	- SB defaults route on server or is this a profile thing and user selectable?
 
-TODO: Widget edit form, new record gives following error because custom field not set that is required:
-	- {"error":{"code":"2200","details":[{"target":"WidgetCustom2","error":"2204"}],"message":"Object did not pass validation"}}
-	- Why is this not displaying right in the UI error box?  It just says "Validation error Object did not pass validation" and nothing else!?
-	- Ok, this is a bigger issue than originally seen.
-		- The server returns as above a normal error json fragment, the custom fields are referenced by their names like any other fields
-		- However, in the edit form each control has a ref and errors collection set by that ref so essentially it's sending "customFields" as the ref name of the entire custom fields control to the error returning code, however there are not matching fields
-			- i.e. the error comes back as for field named "WidgetCustom2" but the form is looking for errors for "customFields"
-		- What should happen:
-			- Custom fields control should participate in the same error code as the main form so it's identical and works
-			- Maybe can just do it like the main form but reference the main form's error collection??
-
-
-TODO: gzform - seems to be assuming that server is returning matching field names as in form but they don't seem to match in case nor with name as for example notes in form is WidgetNotes in server error box:
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[name] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[name] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[serial] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[serial] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[count] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[count] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[dollarAmount] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[dollarAmount] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[startDate] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[startDate] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[endDate] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[endDate] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[active] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[active] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[roles] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[roles] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[notes] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[notes] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[tags] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[tags] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[customFields] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[customFields] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetNotes] to form field ref:[WidgetCustom2] gzform.js:91
-	getErrorsForField finding matches, comparing serverErrorField:[WidgetCustom2] to form field ref:[WidgetCustom2] gzform.js:91
-	- In a custom field the names match exactly
-	- Other fields seem to have no Widget in them at the client end but do from the server end
-
+TODO: Widget edit form, new record cdata error as it's empty on new
+	- To see, create new and edit the custom2
 
 
 TODO: Save button isn't enabling on changes in new record when it should.  Enter in a value in the Name field of an empty record and move to a new field and it should immediately show the save button due to dirtiness?  
@@ -94,10 +61,7 @@ TODO: Save button isn't enabling on changes in new record when it should.  Enter
 
 TODO: Make sure can easily make new record in Widget form before getting into deeper stuff or making any other object forms.
 
-TODO: Widget edit form, new record sb time and dates pre-filled in? Server involved? How to handle new record initial date set?
-	- Don't start blank basically
-	- some objects may be configurable what the default date/time range is so maybe enable that for widget to test
-	- SB defaults route on server or is this a profile thing and user selectable?
+
 
 TODO: Bug?  Set widget edit form times to 4:20pm and observe that in the main grid list it shows as 320 pm!?