Super helpful! Never thought about assigning values to a single record variable and then adding that to a record collection variable. I was needing to map fields from object A to object B inside a loop to create new object B records and that was the secret trick to creating the records outside the loop.
You're such a great trainer, your explanations are super super helpful. I've finally stopped running away from loops and variables 😆and just re-created one of my complicated flows. So happy!
This made my day! Thank you for sharing - that’s my hope, for others to feel confident tackling these seemingly complicated things. (And congrats to you on optimizing that flow!👏👏)
Very nice. Clear. Concise. At the 4:10 mark, you have the 'edit Assignment' screen, you show a variable 'record_newTask>Subj...and it's a text type (or so it appears). At 4:22 mark, you show Edit Assignment-Add to Collection. There I see the 'record_newTask......indicates a record type. How is that?
Thanks for the note! The 4:10 Assignment element is populating specific fields within a single record variable (aka the new task record). The 4:22 Assignment element then adds that same record variable to a record collection. Does that answer it?
I feel the same way but am finally getting comfortable with Flow. Building automations in Flow makes it so others in my org can maintain them too, not just me. The GUI is slow but powerful
Apologies that I'm so late to this conversation! But I have to second the maintenance comment. Having learned to write some code, I agree that it's much faster. But when an org doesn't have a developer resource on staff/can't splurge to get one, this makes sense for meeting the automation need. Thank you for watching!
Super helpful! Never thought about assigning values to a single record variable and then adding that to a record collection variable. I was needing to map fields from object A to object B inside a loop to create new object B records and that was the secret trick to creating the records outside the loop.
Awesome Chase, I'm glad it was helpful!
You're such a great trainer, your explanations are super super helpful. I've finally stopped running away from loops and variables 😆and just re-created one of my complicated flows. So happy!
This made my day! Thank you for sharing - that’s my hope, for others to feel confident tackling these seemingly complicated things. (And congrats to you on optimizing that flow!👏👏)
A fantastic way of explaining. I found it very useful.
Thank you for the comment, I'm glad to hear it!
This really helped me building a flow to create multiple line items from one object to another (through a conversion). Thanks a lot! :)
Thanks Typhaine, I'm happy to hear it!
Thank you, that was exactly what I needed! After I saw it, it made so much sense.
Thanks Mitchell, glad to hear it!
Very nice. Clear. Concise. At the 4:10 mark, you have the 'edit Assignment' screen, you show a variable 'record_newTask>Subj...and it's a text type (or so it appears). At 4:22 mark, you show Edit Assignment-Add to Collection. There I see the 'record_newTask......indicates a record type. How is that?
Thanks for the note! The 4:10 Assignment element is populating specific fields within a single record variable (aka the new task record). The 4:22 Assignment element then adds that same record variable to a record collection. Does that answer it?
Thanks You are the best 😊
UGH! I hate flows so much! So much more logical to write this in code.
I feel the same way but am finally getting comfortable with Flow. Building automations in Flow makes it so others in my org can maintain them too, not just me. The GUI is slow but powerful
Apologies that I'm so late to this conversation! But I have to second the maintenance comment. Having learned to write some code, I agree that it's much faster. But when an org doesn't have a developer resource on staff/can't splurge to get one, this makes sense for meeting the automation need. Thank you for watching!