Hello,
I see that there is a step type “return values from this process” but it is not clear to me how it works.
I am able to create columns with a desired return value but how can I access them in a following step? Are they stored in a specific table?
Thank you.
Hi @Matteo_Menghetti, good question and thank you for the feedback.
You can access the results in the subsequent step using a formula like this: [Previous Step].[Value that was returned]. So for example, it would be [Get the approval].[Decision].
[Previous Step] is kind of a big deal in case anyone was wondering… 
Thank you! I was able to make it work on a step of type Call another process but not on one of type return values from this process.
In the exemple here below I run an action called ADD PC, in this action I set a column called PC, I would like to return its value so I am calling [Add item row].[PC] but I have an error
Am I missing something?
Hi Matteo,
Thanks for trying out our new features.
Any changes that are made to the Entity (Row) that is in the context of the processed can be accessed directly. So if in the “Add PC” step you set the PC column in a later step when you reference the “[PC]” column it will have the updated value…
Is there a way to grab the value from from a decision of “Yes/No”?
Example: I did the
Branch on condition
CONTAINS([Email], “gmail.com”)
If yes call an action that flags the contact as “Y”, if no flag it as “N”
It works great but can I have a single action that updates the value using the result of the conditional check, when I call action “Data: set values of columns in this row”
something like…[Previous Step].[Check if Email contains “gmail.com”]
I am not sure I understand the reasoning behind why you are trying to do this.
If you would like to set a column to the result of ‘CONTAINS([Email], “gmail.com”)’ you can have a data action that will set the result of that expression to a value of a column. There is no need to branch.
If you already have a branch because you need to do other logic you can just set the column value to “Y” in the yes branch and “N” in the no branch.
Let me know if this is what you are trying to acheive.
That make sense. I was kicking the tires and got some tunnel vision. I am curious about how people are using the for each, and other newer functions.
I apologize, the ForEach step is not yet fully available, however it leaked into the currently deployed UI. It will be removed shortly. When it is released we will provide full documentation so it would be easy for you to take advantage of.
I spent hours first time today to examine Automation, but found it is quite difficult to understand.
This was first time to feel tons of difficulties to understand Appsheet features so far I learned amng others.
RETURN value step. In the programming, it means one particular function to return the value. If there is any subsequent steps, they will not executed, as return is sign of the end of process.
If we ended up steps with return step, then we need to move to another step, thats why I feel Appsheet is graying out the following step so that we are not allowed to add any more steps as it wont be processed. This was what I thought.
then as you rightly said, it is troublesome and painful we start to build up the separete process.
But today I faced the problem and difficulties to understand how to pass the previous process return value… On the premier document, return value is used for validation, to see yes and no.
If we think this new Automation as kinda of programming, my assumption was “returned value” could be a sort of variable, either local or global, so those value could be reachable through the new . dot notation.
I tested several time in different scenario how to get the returned value (variable) which was generated by the previous / parent process and push to child process, but I could not find it.
Either way, I found new Automation is quite difficult to understand and handle.
The current action/workflow set ups could be more easy and intuitive, at least to me.
