Thank you!
The first thing I tried was going to Dynamic Attributes then setting VALUE for those two fields and I thought I had followed through with setting up both as variables on this page -- I had a dmx-bind: with what I thought were the value parameters selecting what thought was an expression of the values named in the url.
But, I will try this again now.
As the question about WHY --
I only needed them one time -- on the next page, the actual input form page.
Once submitted I didn't need them again.
As a matter of necessity they need to Disappear as values immediately because the next use of the Form may be using new values for both variables in the same session.
Now let me gripe about one thing that I think by now is just plain WRONG
It is way too easy to upset all of the code just worked on in the Connection Query step.
This has set me back more than once -- to make all of my code useless to display because of the Binding of Queries to a Connection.
Sure, sure -- the intial CONNECTION is simply to one database-- the same database over and over for different queries.
BUT
I then name my Connections separately that I want to BIND a specific Action Step -- a query that may be an insert or simple query SELECT.
I have tried to keep each Connection that is going to have a specific query or queries attached or Bound --- a name --- Server Connection:GrabHotels
Then I want to bind to that connection the next action step which is going to USE a simple Select (whereas on another page I will be using an INSERT query)
What I want is to look like this -- only something like
Database Connection: connection_to_post_form
Database Insert: insert_post_to_form
But for this demo I leave the "default Wappler" name values
I have decided to BIND these 2 Action Steps together because as I understand Wappler best practices it is Useful to do this to help make it easier to use & to be able to grab this same sequence of Action Steps under one distinctive name for application to a duplicate or similar page.
:
But on the APP STRUCTURE side I have this --
Wappler shoves this generic-name serverconnectform2
at me
I cannot choose the Action Steps package I made under MY Named Action
Wappler decides that I only get its own procedure with generic names -- apparently to "represent" what it thinks I want now.
Later on another page when I again make a set of action steps when I go to the App Structure side to ADD SERVER CONNECT component
the only component I can add has, again, a generic SERVERCONNECTFORM2
This is just WRONG
Because now if on a new page I use this NAME it seems to have the last or another in my sequence of previous action steps used --
I am led into believing that I can also specify ANOTHER SERVER ACTION
IF I go down this trail and select say -- insert/post_post_form (from my choice of previous QUERIES)
and SAVE -- somewhere soon after -- I forget what I actually see Wappler report -- I can irretrievably BREAK another page I have worked on.
The ACTIONS I have created and SAVED for another page can be REWRITTEN in their internal parameters & then the previous page -- although not changing any names of connections and action files that I have defined -- it is NOT the same Working Code anymore.
I have probably missed something from my recall of recent history but
this is so EASY to do. --- Building in PHP the code will always work everytime if the connection and functions and classes are not rewritten in the foundation of the application.
At any rate -- this foundational Connections and Action Steps is too prone to an error when working hour after hour or day after day.
I must be able to Save my Connection AND action steps under one BOUND NAME that I assign
and then FIND IT readily available on the App Structure side when I now decide to ADD SERVER DATA CONNECTION COMPONENT to a specific page.
Much is made of the Flexibility of Wappler -- you are basically free to determine your work flow. I follow the flow that the tutorials usually show for Server Connections and Action Steps.
But once Wappler only offers me ITS PROPRIETARY name for that Component
and I must use "Serverconnectform2" then I am on the path
to accidentally BREAKING another page's ability by, apparently, just choosing a different Server Action for this page.