When I place a "Show Form" with an action of "load form" on the on submit area it does load the next form fine. There is a DB Record Loader on the now loaded form in the on submit area and when I hit submit, the form just reloads itself.
The DB Record Loader (on the second loaded form)in the on submit area has Thank you messages on found, on empty and on no param to check and make sure it works. I do not get any of the messages and the form reloads.
Another issue, the DB Record Loader doesn't like this configuration setup either.
DB Field: my_field_name_one
Table: my_table
Request Param: my_field_name_two
Save under Model id: No
It only works when both the DB Field and Request Param are the same. Is this the DB Loader normal action? I assumed that the Request Param and DB Field can be different. By the way the loaded form does have both field names (my_field_name_one and my_field_name_two) available to use.
Thanks
The DB Record Loader (on the second loaded form)in the on submit area has Thank you messages on found, on empty and on no param to check and make sure it works. I do not get any of the messages and the form reloads.
Another issue, the DB Record Loader doesn't like this configuration setup either.
DB Field: my_field_name_one
Table: my_table
Request Param: my_field_name_two
Save under Model id: No
It only works when both the DB Field and Request Param are the same. Is this the DB Loader normal action? I assumed that the Request Param and DB Field can be different. By the way the loaded form does have both field names (my_field_name_one and my_field_name_two) available to use.
Thanks
Hi,
This may be too late but I wanted to note that this issue can be fixed by setting the "Relative URL" setting for the 2nd form to "No", this is under the form's "Edit" page, the new V4RC2.0 should havet his issue fixed by default.
regards,
MAx
This may be too late but I wanted to note that this issue can be fixed by setting the "Relative URL" setting for the 2nd form to "No", this is under the form's "Edit" page, the new V4RC2.0 should havet his issue fixed by default.
regards,
MAx
This topic is locked and no more replies can be posted.
