Requesting a feature as per the old set of Google Sheet integration

Hi,

I noticed that a recent JotForm update changed the way that data is sent over to Google Sheets with you have it integrated with your JotForm.

The data used to update by "updating" (or overwriting) a row in the Google Sheet tab. Now, it appears that a new row is INSERTED instead.

This has removed my ability to have a second tab where I automatically pull, format, update items based on the entries. Formulas on another tab that reference cells in the integration tab will no longer point to the correct cells when a new row is inserted instead of being updated/overwritten.

I noticed that the Microsoft integration with Zapier allows you to choose how the data is ported over and includes an option to "update rows in Microsoft Excel for new Jotform submissions". For a couple of reasons, I cannot use the Zapier integration but was wondering if you could please add this option to the Google Sheets integration.

thanks!

Hi MaryAnn,

Thanks for reaching out to us for help. I understand your concern about the recent change in the Google Sheets integration where new rows are inserted instead of updating existing rows. Currently, Jotform's Google Sheets integration adds new submissions as new rows, which can affect formulas referencing specific cells.

Unfortunately, there isn't an option yet to update existing rows like the Microsoft integration with Zapier offers. We appreciate your feedback and will consider this feature for future updates.

Let us know if you have any other questions.

Best regards,
Jotform Support

The Google Sheets integration USED to simply update existing rows with new submissions. Why was it changed? Can we go back to the previous setup, or be given the option to select how the Google Sheet will collect new submissions?

Hi MaryAnn,

Thank you for your message. A member of our Support Team has taken over this thread and will assist you further. I will no longer be responding here.

Best regards,
Jotform Support

Hi MaryAnn,

If you can take a screenshot of what’s happening, that'll help us to understand better what’s going on. Let me show you how to post a screenshot to our Help Center:

1. On the Help Center page, scroll down to the Your Answer section and click on the Image icon.

2. Drag and drop your image into the Upload box, or click on it and select your file.

3. Then, click on the Add button in the bottom-right corner of the window.

4. To resize it, click on your screenshot and then click on one of the boxes in the corners, and drag it inward.

5. Once you're finished, click on the Post Answer button at the bottom right of the Your Answer section.

That's it. Once we hear back from you, we'll be able to help you with this.

The Google Sheets integration USED to simply update existing rows with new submissions. Why was it changed? Can we go back to the previous setup, or be given the option to select how the Google Sheet will collect new submissions?

This isn't really a screenshot issue. It's how the Google Sheets integration has changed the way it outputs data when a form submission is created. Is there a way to go back to how it used to work ("updating" a row instead of "inserting new row")?

Hi MaryAnn,

Jotform's Google Sheets integration adds new submissions as new rows in the spreadsheet rather than updating existing rows. This is the standard behavior now and, unfortunately, there is no option to revert to the previous setup where existing rows were updated or to select how new submissions are added to Google Sheets.

This change affects how formulas referencing specific cells in your spreadsheet behave, as new rows are inserted instead of overwriting existing ones. We understand how this impacts your workflow, especially with formulas on other tabs relying on static row references.

At this time, the integration does not support updating existing rows, like the Microsoft integration with Zapier does. While the feature you're looking for isn't available at Jotform right now, we've gone ahead and escalated your request to our developers. Exactly when or if it's developed depends on their workload, how viable it is, and how many other users also request it. If there are any updates, we’ll circle back to this thread and let you know.

Thanks for your patience and understanding, we appreciate it.