- MasalamediaAsked on February 18, 2013 at 01:46 PM
Not all, but some submissions are sent to my Google Spreadsheet more than once. I've re-integrated at least once since the problem first showed up. The submissions do not appear more than once in the Jotform database.
- MasalamediaAnswered on February 18, 2013 at 01:51 PM
Other multiple instances of a submission on this particular integration include these sumbission ID's
That's 4 of 7 unique contacts, more than 50% failure rate.
- JotForm SupportMike_TAnswered on February 18, 2013 at 03:21 PM
We are sorry for the inconveniences caused.
I have created a bug report ticket about this integration issue, and forwarded it to our Development Team.
We will get back to you with update on this thread once we get any news.
- MasalamediaAnswered on February 20, 2013 at 11:21 AM
This has really pissed off the client. As far as they're concerned, I've foisted an unreliable technology on them. They're asking the reasonable question: if some entries are being duplicated, then how do we know some aren't being lost altogether?
They're asking me to move their forms do a different service. I will hold them off for a few days, but its a huge cost-loss to me if I have to do that. I really wish you'd solve these basic problems.
- JotForm SupportEduardoMendezAnswered on February 20, 2013 at 12:02 PM
Our dev team is working on a solution for this.
We apologize for the inconveniences. Meanwhile, have you looked into our HTML listing report, It will provide a spreadsheet that can be embedded on a web page or a form and dinamically updates as a Google spreadsheet would. If that can be a temporary back-up, here is a guide to help you with that:
- MasalamediaAnswered on February 20, 2013 at 12:05 PM
That does seem like a workable solution in one sense, but I've built systems and training around the GoogleDocs integration already so this workaround would require unbillable time to build a new system and a team of people on a new procedure. That's costly.
- JotForm SupportEduardoMendezAnswered on February 20, 2013 at 12:21 PM
Our sincere apologies!
We are working to have this resolved. In fact, one of our developpers has been assigned to the ticket and it has been marked as "Important" in terms of priority.
As soon as there is a solution to this issue our dev team will update this thread.
In advanced, we thank you for your patience.