In the older version of Wappler whose actions are still depicted in some Wappler Tutorial docs when a Connection is made to start a Form page, for instance, I would first pick out the connection itself and add it at the tiop of the Design… All it did was specify the basic database connection.
And, though the default was “Serverconnection1” I could SPECIFY the Connector I had created with a name such as “LocalTrainingsDB” and the connection would change from the default “Serverconnection1” to my own “LocalTrainingsDB”.
4.4.5 does not enable me to choose an already named connector file I had saved.
But, NOW I must Add the ACTION or API to save this Connect to Server setting.
However, when I now want to specify an API to Insert field forms to my online table this next form action again specifies that I must dhoose the same API that I defined in Step One.
I am expecting, as the old Wappler, that i do not, and can not, select the actual Action or API i created that will INSERT the fieles to my table.
I am confused. In 4.4.5 I am now specifying the SAME Server Action TWICE at the top of my form. I’m having inconsistent Inserts.
The form may Save to my database the 1st or 2nd rime, but then fail over & over after that.
What is happening when the initial Server Connection file in a page requires assigning the same API that I am going to also set in my next server action which is intended to save the form values that will posted from this form?
What is the way I should be creating this Insert to Table action in a new form page in 4.4.5?
Last updated: