ZachCase
8 years agoQrew Trainee
What Does This Hidden Input Do, and Is It Safe to Remove for a Specific Use Case?
I am adding some functionality to a form that has a field that quietly updates the RedirectURL to a code page we have created. To get to this form, a user comes in from an "Add Entry" button on a record view. When we save the form, the RedirectURL is not respected and instead, we are taken back to the record view. I was troubleshooting as to why, and came across this hidden input that, when present, stops the RedirectURL from being respected. However, when I remove said hidden input, the RedirectURL value is respected and I'm taking to my code page.
The hidden input is: input type="hidden" name="z" value="ddbm"
I assume based on the tests that this just tells Quick Base to return the user to the record view the request originated from. Is there anything else special about this hidden input? Or can I safely delete this input dynamically when I need the RedirectURL to be respected even when the request originates from a record view?
Couldn't find any documentation on it from searching Google, so I would feel a lot more comfortable if I just got confirmation that removing this element won't break anything.
The hidden input is: input type="hidden" name="z" value="ddbm"
I assume based on the tests that this just tells Quick Base to return the user to the record view the request originated from. Is there anything else special about this hidden input? Or can I safely delete this input dynamically when I need the RedirectURL to be respected even when the request originates from a record view?
Couldn't find any documentation on it from searching Google, so I would feel a lot more comfortable if I just got confirmation that removing this element won't break anything.