Great Video and could clearly understand you! I have a flow for a hospital - it writes records to SF Cloud. When an error occurs in writing the record (duplicate or inactive user) I capture the error messages in a Compose (using "Body") and I can scroll thru the output and see the errors. The status or error code is too generic and I need to parse the 'error messsage' to get the actual issue. In order to SEARCH thru the ERROR "Message:" for the phrase "duplicate" - do I have to place the COMPOSE outputs into an array variable and then search the array ?
Hi Mark, apologies for the delay in replying. I've not seen any performance differences using one over the other, certainly in the use cases where I've used them. The choice purely comes down to the how I'm going to structure my flow and if I need to use it more than once
Have you found a way to rename "Outputs" so that it's not so generic? Right now, that seems like a big downside to compose that you have to hover over where "Outputs" is used to see which compose operations it's a result of.
Thank you for this very helpful intro to compose and variables! A great way to start learning how to use flows beyond the prebuilt templates.
So well explained and easy to follow...
Very nice and informative video Thx :)
Great video an easy explanation, it was what I needed. :) Thank you
Nice and clearly explained
Great video Matt, thank you.
Absolutely!
Fantastic Matt, this video helped me a lot! Thanks for all the infos.
Thanks a lot Matt, it was great and informative video.
Nice explanation Matt. Also may I know which video editor you used for recording this video.
So in a nut shell, use Compose to store constant values, and variables to store values that will change.
Great Video and could clearly understand you! I have a flow for a hospital - it writes records to SF Cloud. When an error occurs in writing the record (duplicate or inactive user) I capture the error messages in a Compose (using "Body") and I can scroll thru the output and see the errors. The status or error code is too generic and I need to parse the 'error messsage' to get the actual issue. In order to SEARCH thru the ERROR "Message:" for the phrase "duplicate" - do I have to place the COMPOSE outputs into an array variable and then search the array ?
Hi Matt. Definitely need to put something in the diary for a catchup :) A quick question. Is there a performance benefit to using one over the other?
Hi Mark, apologies for the delay in replying. I've not seen any performance differences using one over the other, certainly in the use cases where I've used them. The choice purely comes down to the how I'm going to structure my flow and if I need to use it more than once
Have you found a way to rename "Outputs" so that it's not so generic? Right now, that seems like a big downside to compose that you have to hover over where "Outputs" is used to see which compose operations it's a result of.
how to combine two big arrays