Create Multiple Rows in Table from a ADD Form Values

Hi,
Am Trying to recreate an Application from Appmaker and coming across many Problems.
In the present scenario:
Want to Populate a Table with multiple Rows of Data From a ADD FORM.
in which case most of the Fields should be the same apart from some.

Any suggestions will be very much appreciated !!

Thanks in advance

This is possible with form onsave events or workflow rules / api calls.

The benefit to workflow rules is they are more flexible / customizable and in some ways reliable than onsave or in app actions.
The downside to workflow rules is they occur in the background and therefore no immediate indication that they have worked is given to the user.

If you could provide some more information about your form, how you plan to indicate how many rows it should add, and how to differentiate between the rows, I could offer more advice.

1 Like

You might also check out the “Add a row to another table” action

2 Likes

Hi Jonathon,
Thanks for your Reply.
I have FORM with fields in the Form:

Id (Auto)
COD (NUMBER)
NAME (STRING)
START DATE (DATE)

OFICINA( This is a multiselect from TABLE OFICINA)

ZONE (DROPDOWN FROM TABLE ZONE)
AREA (DROPDOWNFROM TABLE AREA )
PROYECT(DROPDOWN FROM TABLE PROYECT)
CLIENT (DROPDOWN FROM TABLE CLIENT CLIENT )
OBSERVACION (TEXT FIELD)
ORDER_BY(EMAIL OF THE PERSON CREATING- INSERT AUTO).

Now the objective is:
USER CAN SELECT from multiselect FIELD OFICINA x No of OFICINA (eg. VALENCIA, MADRID, BARCELONA)
and fill rest of the Fields.
ON CREATE, POPULATE new ROWS in TABLE SUBPROYECTOS depending on the no of values selected in OFICINA.
REPETE all the Values in Rows expect the field OFICINA which will change on multiselect values.

Hopefuly I was able to explain properly.

1 Like

Here is one user friendly way of achieving this. In a nutshell you will:

  • Create form_RowGen[1] actions which copy the record but select singular OFICINA() items
  • Put them in a grouped onsave action

Here is the app definition:

Feel free to copy the above sample and play around with it.


One obvious limitation of this method is you need to have at least as many form_RowGen[#] actions as your users will be expecting to generate in one go. Worst case scenario is you would need a new rowgen action for each ‘Oficina’ option.

I can think of a possible way around this by using an ‘execute action on set of rows’, where you SELECT() from the Oficina table and run against those rows, but I don’t have time to test it right now.

3 Likes

Thanks a lot Jonathon,
I will try to follow your example.
Greetings from Spain

1 Like