ayanova/devdocs/todo.txt

@@ -6,7 +6,9 @@
 MISC ITEMS THAT CAME UP
 todo:formcustom form is not localizing on the fly, it was expected that it would be entered via the objects edit form but this is not always the case, e.g. record history form etc
 	Make it fetch on the fly like the datagrid or however is most appropriate
-todo: history items, fetch locale text in name as appropriate if it has the lt:, I think there is already code to handle this scenario extant, maybe in form errors?
+
+
+
 todo: idea - move sublists into menu option in grid list and edit form
 	e.g. Unit Models doesn't really need to sit always in the nav panel to the left and it's getting crowded in the service "pane" anyway so
 	Move the unitModels into the menu of the Units list and into the menu of the Unit edit form and remove from the Service nav panel

ayanova/src/views/ay-customize.vue

@@ -385,9 +385,21 @@ async function initDataObject(vm) {
   //Iterate ObjectFields
   //create a new object based on the f.a.f. item and any existing template values for that item
 
+  //Iterate first  to ensure the cached translations of field keys 
+  //(due to this form being opened directly from things like record history so might not be cached yet)
+  let requiredTranslations=[];
+  //for (var i=0, l=arr.length; i<l; i++)
+        //if (a.indexOf(arr[i]) === -1 && arr[i] !== '')
+          //  a.push(arr[i]);
+  for (let i = 0; i < res.data.length; i++) {
+
+  }
+
+//Iterate a second time to build the working collection
   for (let i = 0; i < res.data.length; i++) {
     //get the formAvailableField record into an object to save typing
     let faf = res.data[i];
+ 
     //get the customTemplate record for this field if it exists
 
     let templateItem = window.$gz.formCustomTemplate.getFieldTemplateValue(
@@ -419,5 +431,7 @@ async function initDataObject(vm) {
       vm.formCustomTemplateKey
     );
   }
+
+
 }
 </script>