Relative path for variables (eg iformbuilder.math.sum) or passing data to parent

Follow

Hamish

December 28, 2014 11:34

As I understand it you always need to use the full "path" name when accessing child variables in a parent or when using built-in functions

eg iformbuilder.math.sum(table_name.subform_element_dcn, 'element_on_subform')
(https://iformbuilder.zendesk.com/hc/en-us/articles/201697610?)

This means that if you copy the parent form or rename it you need to update the javascript for that aggregation.

It's the same for passing data around.
https://iformbuilder.zendesk.com/hc/en-us/articles/201697700-Pass-parent-data-to-subform-subform-to-parent-

It would be much better for reuse and supportability if there was a mechanism to state <current_record> and hence use not explictly state the parent table & path.

eg iformbuilder.math.sum($current_record.subform_element_dcn, 'element_on_subform')

where $current_record is evaluated as the name of the parent table (and any higher level parent records).

Not sure if I've made that clear - or if iFormbuilder or Javascript has a mechanism to do this already.

6

• 

  blake January 09, 2015 15:18

  If I could upvote this a hundred times, I would. Would make copying / versioning forms so much easier.

  0

  Comment actions Permalink
• 

  Hamish February 24, 2015 06:21

  Good suggestion from one of the iForm guys is to put all of the javascript that includes absolute paths into the page level javascript - at least that way it can all be changed in one place for all the sub forms.

  0

  Comment actions Permalink
• 

  blake February 24, 2015 12:43

  I've tried that, but having a hard time reliably triggering the functions to run. Any tips?

  0

  Comment actions Permalink
• 

  Hamish February 24, 2015 21:34

  Apparently one key thing is that the javascript functions etc must be in the highest parent page level javascript. IE page level javascript in child forms will not be found is my understanding. I'm using function calls.

  0

  Comment actions Permalink
• 

  Hamish September 02, 2015 05:02

  Blake - did you figure out how to separate this issue into a single function call - I haven't figured out how to do it.

  0

  Comment actions Permalink
• 

  blake September 10, 2015 14:52

  This should work, but I haven't tested extensively. The trick, as best I can tell, is that you have to somehow trigger the JS in the Dynamic Value to run. Without the IF, it won't work. With it, it does. I have to do something similar when I have a function that is dependent on multiple widget values - write an if with a bunch of OR's on all the fields and it tends to work.

  Having said that... it doesn't really address the issue raised above since the IF statement still contains a reference to the parent form name... which is what you (and I) were trying to avoid.

  Page JS:
  function GetValue1(){
  return function_main.subf[0].value1;
  }

  Dynamic Value:
  if(function_main.subf.length > 0){GetValue1()}

  0

  Comment actions Permalink

Please sign in to leave a comment.