Incorrect Data Transmission from User-Specific Columns to Zap Actions

[constantinos_christo]

First time reporting a bug? Refer to our Start Here post.

---

Team ID:

• In the Glide dashoard URL, e.g.
  https://go.glideapps.com/o/qtZ1asZBpzDVxNNaKSld/

App ID:

• In the Glide builder URL, e.g.
  https://go.glideapps.com/app/oKN6hMp7AhFHyvIDQxpk/layout

Description
I am experiencing an issue with a custom form in my Glide app that utilizes user-specific columns. The form is designed with a submit button that is linked to a custom action performing the following sequence:

1. Adds a new row to a specified table, incorporating data from the form’s user-specific columns.
2. Triggers a first Zapier automation (referred to as “Zap”).
3. Waits for three seconds.
4. Triggers a second Zapier automation.
5. Clears all values within the form fields.

However, I’ve identified a recurring problem with the first zap, particularly concerning data synchronization. When the form is submitted, the first zap should transmit the current value from the user-specific column (which is assigned to “Value 1”). Instead, it erroneously sends the value from the previous submission. For clarity:

• On the first submission, if “Value 1” is ‘1234’, the first zap processes and sends ‘1234’ correctly.
• On the second submission, if “Value 1” is ‘5678’, the first zap should send ‘5678’. Contrarily, it mistakenly sends the outdated ‘1234’.
• On the third submission, changing “Value 1” to ‘0987’ should result in ‘0987’ being sent. Yet, it incorrectly uses ‘5678’ from the second submission, demonstrating a persistent lag in data synchronization.

Interestingly, this issue does not affect the second zap, which accurately reads and transmits the correct value each time, regardless of the submission sequence.

The “clear values” function in the form appears to operate as intended since the newly added row in the Glide table reflects the correct, updated value. This inconsistency suggests an issue in how the first Zap retrieves values from user-specific columns, leading to incorrect data transmission.

How to replicate

• Currently, the specific conditions triggering this issue are unclear, making it difficult to reproduce consistently. It occurs irregularly and does not seem to be influenced by distinct user interactions with the form, as confirmed by user feedback.

[ThinhDinh]

How are you changing the value of “Value 1” between the two Zap submissions?

[constantinos_christo]

The process for altering “Value 1” between Zap submissions, as experienced by the user, is outlined in the following steps:

1. Selection: The user selects a specific row from a collection within the app.
2. Detail Screen Display: Selecting the row leads to the display of its detailed screen, which showcases all pertinent information related to that row.
3. Pre-filling Form: At the top of this details screen, there’s a title accompanied by a custom action. This action is designed to pre-fill the user-specific fields in the custom form based on the selected row’s data. After setting these column values, the custom form becomes visible to the user.
4. Form Completion: With the fields pre-filled, the user can then complete any remaining sections of the form.
5. Submission and Triggers: Upon submitting the form, a custom action is activated, which sequentially triggers the zaps.

Thus, the values that the zaps utilize are initially cleared following each form submission. They are subsequently re-established based on the values from the detail screen when the user initiates the custom action as described in step 3. This ensures that with each new form submission, fresh data is sent through the zaps, contingent on the user’s selection and form completion actions.