I am trying to use hidden fields to get some information from the form url that would be loaded to be used for parameters in an API connector url and post body.
I first started by creating the hidden fields and set 1 option for each field. I found a setting in Data Tracking to Save URL Parameters for Embedded forms to see if that would help too.
I included the hidden fields copied from the hidden tab of the field reference into the url of the api connector, as well as for the value in the request body and the ui validates them (I mistyped initially and got red errors).
However, if I try to use the test url or the live url it never seems to save the hidden fields in the response if I append them as qs params even if I paste them into the url for each step of the form.
Is there another configuration or step I am missing here? Will they only be saved if they are present on the step that completes the form? Is there a better way to solve my challenge?
The form itself has several steps on it, and the api connector is not invoked until the third step after collecting some other information.
The ideal situation would be that on the initial url loaded (or embedded) would contain sp_id=123&template_id=456 params that could be used in the connector call.
Hey @eri You are correct. I had to make them as standard input fields and hide them on the first step so I could move forward. Even when they were created first using the same names they still did not populate.
I think the issue might have been that I was trying to append after the fragment that gets added when you generate the test form url as opposed to before.
