JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
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.
Inventory Widget: Available quantity does not correlate with received entriesAsked by aaronwatts on November 03, 2015 at 02:59 PM
We are using the inventory widget on this form:
The ticket cap is set to 385.
To date we have sold 154 tickets.
If my math is correct, there should be 231 tickets left.
The widget is reading 251 left.
Thank you for contacting us.
A bug report ticket has been attached to this thread and escalated to our Backend Team for further investigation.
We will keep you updated via this thread.
Thanks. Any help would really be appreciated. We are starting to get reports from field staff across the country. Some of the inventory counts are way off.
Another question. While a solution is being sought, can I just go in and adjust the counts manually. It will be more work, but some of the counts are way off, and we have no timetable for any resolution.
Thanks for all your help.
We understand that you need it working.
In my honest opinion I would recommend that you make a clone do whatever you want for it on the copied form since sometimes it is better to let our Backend see the problem as it is on the original so that we can fix the issue more accurately. Whereas if you made changes it might not be as helpful unless we are able to replicate it again.
However, I believe it might work though I can't make any guarantees including the fact that it would likely cause possible confusion for you perhaps. But, you certainly have that right to try to reset it if you wish to do it that way and you may want to download and make a backup of your submission data beforehand if so or at least until our developers can help to resolve it.
I'm sorry this took a while to resolve.
It was in relation to a database issue - which we have resolved.
Accurate counts have been restored.
We apologize for the trouble this caused you.