I have a protected form that has a hidden account control field. In the render function, I set two more hidden fields to capture the Name and Email of the user submitting the form.
Upon submission, the form triggers a power automate to both create a Docusign envelope and send the form details to our SQL database. Sporadically, the 'SubmitterName' and 'SubmitterEmail' fields are coming in blank.
Any ideas on why that's happening? Some of the forms are just set to only allow Authenticated Users, some are restricted to specific groups. Most of the time, the fields are populated. Unfortunately, I don't have details on if it's specific users or something about their environment, which I know makes it really difficult to pin down. I'm just wondering if anyone has come across this issue before, and what they did to resolve it.
There are no errors in the PA flow. It looks like on occasion, the hidden text fields that are supposed to populate the account's name and email are not being populated, and thus are being added into the SQL table as Null.
In an example from 11/22, two forms were submitted. At 3:06pm, the 'SubmittedBy' and 'SubmitterEmail' fields were populated & inserted into the SQL table correctly. At 3:09, the fields were not in the JSON data that triggered the form. So I think the error is occurring when there forms are submitted back to back.
Is the rendered function called after a form is submitted? Or only when the page is refreshed? I've attached the relevant section of the function.
I'd still like an answer to the question above, just for my own knowledge, but looking at the form data that triggers the flow, I'm thinking it would be better practice to get the user info directly from the JSON.
Just looking at the data, I made the assumption that users were submitting forms without reloading the page, and this was causing the account details not to load & populate the fields.
This particular scenario hasn't occurred since I put in the ticket, but using the JSON data in the Power Automate to fill out the fields for the SQL Insert seems to be working fine, and it comes in each time a form is submitted.
If it reoccurs, I'll create a form to reproduce the issue, but I think we're good. Thanks for your help
