What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
How to ensure that the published submission view is the latest fully populated versionAsked by guineapigme on March 01, 2015 at 01:08 AM
Because I am having so much difficulty with printing, because of the bugs in the print of the edit version of the form, one of my workarounds is to have the user go to the submission view and then choose print.
However, hte view at the stop of the heap is not always the most recent. How do I ensure that the latest/greatest submission is the one that will come up for the unsophisticated user when they access that link?
I would remove this option if I had the bugs fixed from the print of the edit form.
In the meantime, this is the only valid way to get ALL the form information, so it is essential that there be some way to see the last version of the form without having to use the back and next arrows to find it.
Am I misunderstanding something fundamental?
If I understand your issue correctly, I take it that you would like for the most recent submissions to be shown at the top of the list in the data grid in View Submissions?
If so, for you to get this done you can simply sort the data grid by submission date by clicking the column whenever you visit the View Submission interface.
You can also partially download your submissions. This feature allows you download submissions between two different dates. You can read more about it here: http://www.jotform.com/help/73-How-to-Partially-Download-Form-Submissions-as-Excel-CSV-PDF
I hope this helps.
Is there a way to set this as a default view rather than clicking each time on the submission ID?
I have very unsophisticated users and I am only using this as a workaround to the problems I have with the a bug in the Printable version of the editable version of the form.
Sorry to say but base on my checks there are no procedures in place to have a field set to sort by default when you open the View Submission interface.
There is another option that you can explore. Would you like to send your submitted information to a Google Spreadsheet? That way you can easily track the latest submission by checking the end of the file. You can view this guide for more info: http://www.jotform.com/help/228-How-to-Integrate-Form-with-Google-Spreadsheet
Is this a possible work around for you? Please advise.
Ah, thank you, but no I don't think this is a good option for my target audience of this information.
All of these machinations I've been trying lately is to get a formatted view of my form to be able to print out for the users. A spreadsheet view would be inappropriate for the target audience.
I am trying to work around so many issues with the OTHER suggested workarounds to get something better formatted than the "Get PDF" or generated pdf link.
I will abandon this submission view strategy for now (which is too bad because it had a correct view, just not the latest/greatest by default).
Unlike the submission view, which was always, at least correct ...
My current bug threads all have to do with the other suggested alternative, to print a formatted version using the print button within the editable version of the form.
I am seeing so many intermittent anomalies with this solution (missing lists, phantom page breaks) that I am suspicious of weird caching and race conditions.
Ok. I understand but I am not absolutely sure why you are encountering so many issues with your form development. Hopefully the other possible workarounds in process will fix all your other issues. But as it relates to the this issue, sorry that my suggested workarounds would not work out.
Do not hesitate to open another thread if further issues arise. We will always be here for your support.