error using return value from "call a script" in next step

Hi all,

I have problems using the return value from "call a script" in next step:
Data action 'setze Gdoc ID und Status Action' uses an invalid new column value expression '="https://docs.google.com/document/d/"& [Erzeuge_Gdoc_mit_Fußzeile].[Output]'. Unable to find column 'Erzeuge_Gdoc_mit_Fußzeile'

The bot has a task "Erzeuge_Gdoc_mit_Fußzeile" with a text return value (google docs id):
Joachim_Mund_1-1675322996935.png

it says use [Erzeuge_Gdoc_mit_Fußzeile].[Output] in a process expression.

The next data action task sets a column "Schreiben Datei" with "https://docs.google.com/document/d/"&
[Erzeuge_Gdoc_mit_Fußzeile].[Output]

If I save the appsheet version I get the above mentioned error:
Data action 'setze Gdoc ID und Status Action' uses an invalid new column value expression '="https://docs.google.com/document/d/"& [Erzeuge_Gdoc_mit_Fußzeile].[Output]'. Unable to find column 'Erzeuge_Gdoc_mit_Fußzeile'

Could anybody please tell me, what I am doing wrong?

Thank you, Joachim

Solved Solved
0 4 279
2 ACCEPTED SOLUTIONS

Hi all, I found the solution for my problem using the return value of a google script in the next data action.

It failed with an error message if the data action has turned on linking to use this component in other bots/processes.

If I use a data action with no reusable component it worked.

Don't know why.

Have fun!

View solution in original post

Right—that’s the documented behavior. The reason is that a step that references a prior step’s output can’t do that in multiple processes since the prior step exists only in a single process. 

View solution in original post

4 REPLIES 4

Is the process for a table whose Filter out all existing rows? property is enabled? I've encountered problems referencing values generated within an automation in that scenario.

If that's not the problem, then in an effort to isolate the issue, you could add a different Call a  script task that returns a value and then reference that value in a subsequent step. If it doesn't get flagged as an error, then the issue is something specific to your current step.

Thank you @dbaum "Filter out all existing rows?" is not enabled.

I will try another step in a demo app.

Hi all, I found the solution for my problem using the return value of a google script in the next data action.

It failed with an error message if the data action has turned on linking to use this component in other bots/processes.

If I use a data action with no reusable component it worked.

Don't know why.

Have fun!

Right—that’s the documented behavior. The reason is that a step that references a prior step’s output can’t do that in multiple processes since the prior step exists only in a single process. 

Top Labels in this Space