Sitecore form save data action only creates one form entry for multiple submissions

Question

We have a form on our JSS site's home page. When submitted, it uses sitecore's built in "Save data" action. However, it looks like when you submit the form multiple times, all rows in the FieldData table are linked back to the same form entry row via the FormEntryId column: top table is form entry after two form submissions, bottom is field data.

This makes it impossible to separate the field data across different form submissions. Is there a setting I'm missing that would allow a new FormEntry row to be inserted per form submission?

Update: It looks like this only happens when the form is submitted multiple times between page loads. Refreshing the page and submitting the form again creates a new form entry.

Answer 1

The SavePostedData method in the Sitecore.ExperienceForms.Processing.Actions.SaveData class is responsible to construct the FormEntry object and store it using the defined FormDataProvider. The FormEntryId of the FormEntry object is initialized with the form SessionId.

The form SessionId, also rendered on the form's fxb_<formId>_FormSessionId hidden input field value, is initiated with a random new ID for every page request (implemented in Load method in Sitecore.ExperienceForms.Mvc.Controllers.FormBuilderController class):

this.FormRenderingContext.SessionId = ID.NewID.ToClientIdString();

To answer your question, there isn't a setting to override this implemented behavior. The assumption (and best practice) behind this implementation is that when a successful form submission occurs, the user would be redirected to a new page (using the OOTB RedirectToUrl submit action) or a success message would be rendered on the page in place of the form (rendering a second form page with the success message).

When rendering a success message, you have the option to include a link to the current page in the message to invite the user to enter a new form submission, that would reload the page upon clicking it.

Answer 2

There's probably a more direct solution to the problem, but I got around this by writing a custom submit action to save the form entry and field data rows to the db with a unique guid each time