Hi Tom,

I see a few complexities with this approach but would certainly be open to ideas on how this could work.

Many responders like to see a submission number visible in their form as they fill it out. This provides an easy to reference number to quote if they don’t know where to find their responses (particularly for public facing forms).
This is achieved using the “submission number” component. However if this number is generated when the user submits then no submission number can be displayed as you fill out your draft.
If you’re trying prevent gaps in submission numbers then this does not completely solve the issue. For example if a response is deleted you will still have missing numbers. If you re-use deleted numbers then your numbers are no longer chronological.

Hi Erin,

Thanks for the response.

If the response is deleted before a submission number is generated, wouldn’t the next newly submitted form simply take that number?

Erin Dwyer

Hi Tom,

That is an ideal situation, however a response could easily be deleted from a long time ago. For example in the scenario below:

User1 submits a response using submission number 100
A week passes and the submission number has now incremented to 150 due to other users submissions
User 1 deletes there submission 100

You now have a gap in your number sequence. If you re-allocated that number to a new submission you end up with number jumping from 150 to 100 then back to 151.

Tom

Can it be programmed to only delete the submission but not the used submission number? therefore it can continue the count

Erin Dwyer

Yep that could certainly be the behavior but then we are back at square one of our initial problem where there can be gaps within the submission numbers. Not to mention the new issue of not being able to display a submission number when filling out a draft. Overall I think the current implementation seems to work in more scenarios.

Submission Numbers Generation