Error with "Adding a Row" to Google Sheets

(Yun) #1

Hello there,

I’m trying to add the “Description” of my stocks to another spreadsheet called “Order” based on what the user had selected in my “ask_item” question, which are numbers as choices.

However, when I input the code as seen from above, the bot only populate the “Order” spreadsheet with the 1st description found in my “Stocks” spreadsheet.

I had done this without hiccups with another flow but it’s just not working in this flow.

(Kellsey Shaw) #2

Hi Yun,

The Collections Outputs (used to read rows from Google Sheets results) doesn’t support nested outputs.

You would ideally need to search for a certain row using the users answer so that you had just one result.

(Yun) #3

Hi Kellsey,

What do you mean by “Collection Outputs (used to read rows from Google Sheets results) doesn’t support nested outputs” ?

It was still working last week in another flow of mine. And it is still working now if I run that flow.

(Kellsey Shaw) #4

Hi Yun,

Collections Outputs are used to access your Google Sheets results but the only thing that you can nest inside the output is a number or asterisk.

So you could use:

{{connect_to_stocks.results_+_gsx:description 1}}

{{connect_to_stocks.results_+_gsx:description *}}

But {{connect_to_stocks.results_+_gsx:description 1{{another output}}}} is not valid. This is a output nested inside another and we don’t support that in our platform.

(Yun) #5

Hi Kellsey,

I still have the flow that allows me to nest an output inside the Collection Outputs.
It was still working a few days ago and I can personally send you the proof through email.

I need this feature to be working again as I had to update another spreadsheet with the “choice” that my user had selected. So is there anyway you guys can fix this back again?

In addition, can I assign an “attribute” to the output (choice) selected by my user and nest it again back in the Collection Output statement to achieve the same?

(Karen Barker) #6

Hi Yun,

We haven’t changed anything with how collections works recently and this isn’t something we have ever supported.

By default we would always select the first item in the collection. I suspect that this is what has happened when you have seen it appearing to work.