Re: Update child without opening

Home Forum Parent-Child Forms Update child without opening Re: Update child without opening

#4625

ijobling
Participant

As you have seen there are many ways you could look at this. The idea of presenting the child information into the table is one way to look at this, but in terms of users adding information into the table to then initiate a ‘new’ child form, I think that is very limited and will restrict you further down the line. Certainly it will make what could be a very simple process a lot more complicated if you need to be looking at using the API as well.

If your underlying concept is for the ‘parent’ form to be the ‘summary’ if you like of all previous requests and then from there you users can then raise more requests for time off, you could also look to use a REPORT instead of the parent to present previous information and where they can then initiate a new ‘child’ form if required. There wouldn’t then need to be any parent/child… just the main form the users complete to book time off

But taking this either as a FORM instead of a report, I would perhaps consider the parent form as the ‘summary’ where there is a form connection that returns to the table all the details from the child for that user (as the form is opened, and you can have a ‘refresh’ button that uses the ‘submit and reopen instance’) using form connections as opposed to the get/set field can give you more functionality (have a look at how the ‘connect’ and even ‘connect and search’ behaviour works especially perhaps in terms of how the ‘send parameters’ can be used to filter your connection information.

But then you can have form scripting/behaviours that can work on that table data to present to the user information relevant to your goal (ie time left you can take off etc) and within that could be showing/hiding the ability for them to initiate a new child (ie book more time off).

Then they can initiate a new child form which is the actual ‘time off request’ form, completing all the required information and submit it, and that then follows its own routing path. You could then use the parent/child (or form connection) methods to prepopulate the child form with the users information from the parent so the user doesn’t have to re enter lots of information manually, so in practical terms would then just be entering information for that specific request

Separate reports can then be set up on the child forms to present other information not only to the user, but also to management as well as they may require different information (ie more of a ‘summary of all my staff’)

and I would see that being a much simpler process to get what you are looking for here.