How Can We Improve the Usability of the JSON Creation Process?

Bugs
1

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

Hi team, not truly a bug but the usability of this part to create a JSON is quite terrible. I recorded some of the common issues. Worse things happened in the minutes before and after the recording. Like the clear button not having a “Are you sure” option, pressing enter creating a new row instead of accepting the auto-suggest, and if you change the value of auto create to True, it just delete the entire JSON you’ve created and there’s no way to get it back. This functionality could really use some love and I imagine it would affect many connectors.

2

If you close the search box on a field, it also closes the entire menu. Every.Time.

3

And when you choose Select Path on the values it also closes the entire menu again.

4

Yea that’s pretty clunky. For bigger and more complex inputs like that, I’d probably recommend defining that payload in a step before that one and export the array, then reference it in that input.

5

I see. Like a python step that creates the json and then load that variable. You may have saved me from some gray hairs :sweat_smile: I’ll try that next, thanks.

6

Note that extra steps increase the memory requirements of the workflow.

7

Yeah I already ran into that problem today. It’s a good work around but it increases credit usage.