Why Can't I Scroll Upward to See All Data Entries in Both v2.0 and v3.0 Builder, Making My Workflow Unusable?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi, i having problem using the builder. I cant seem to scroll upward to see all my other data entry. This problem started with the release of v3.0 builder. I initially switched to v2.0 builder and it was still working. Now i need to update my workflow BOTH v2.0 and v3.0 have this bug unable to scroll but, making it literally unusable. Can please help

Screenshot 2024-05-31 at 5.47.39 PM.png
Screenshot 2024-05-31 at 5.47.39 PM.png2880×1800 536 KB

2

Hey , thank you for reporting this issue!
I’ve create a ticket here and add it to Pipedream internal backlog!

For now as a workaround, you can:
• Switch to Pipedream Builder v3
• Add the Node.js code step to map the values needed in your Google Drive action > Replace text placeholders prop, such as it will return the object matches the expected value, for example

// To use previous step data, pass the `steps` object to the run() function
export default defineComponent({
  async run({ steps, $ }) {
    // Return data to use it in future steps
    return {
      "NAME": steps.trigger.event.newRow[9],
      "AGE": steps.trigger.event.newRow[12],
      // ... other fields
    }
  },
})

On your Google Drive action > Replace text placeholders prop, use the Custom Expression and pass the result in the new Node.js code step

3

This is still a massive headache. It should have been fixed already.

4

I can’t access my field list to make crucial updates. Please raise the priority on this.

image.png
image.png917×1191 55.9 KB

5

Hey ,

It’s in the Backlog, and the Pipedream team is evaluating it (cc @U052C338AQK please take a look at this ticket when you have time)

For now as a workaround, you can:
• Switch to Pipedream Builder v3
• Add the Node.js code step to map the values needed in your Google Drive action > Replace text placeholders prop, such as it will return the object matches the expected value, for example

// To use previous step data, pass the `steps` object to the run() function
export default defineComponent({
  async run({ steps, $ }) {
    // Return data to use it in future steps
    return {
      "NAME": steps.trigger.event.newRow[9],
      "AGE": steps.trigger.event.newRow[12],
      // ... other fields
    }
  },
})
6

, @U05PKP3RAHL - we just pushed a fix for this. Can you please let us know if you’re still seeing the issue?

7

The container scrolls now. I can access the fields. Thanks for fixing.