Thanks for this video. With this Transform element, can we create multiple records from Source to multiple records to Target? We have Master Opportunity and Child Opportunity. Each Master opportunity will have more than 1 opportunity line item and all the line items has to be created to all the child opportunities. I have the solution but with loop in a loop and DMLs with in the loop. How to tackle this situation? Help is much appreciated.
First really nice video. Second, in my use case I came accross, what seems to me, some limitations...can you please advise? 1. In the Transform element, let's say we want to set an hardcoded string in the target data, such as any StageName for Opportunities. Is this possible within the Trasnform element? 2. In the Transform element I'm using Opportunitis collections, where I mapped 4 or 5 fields. Now I want to iterate on the target data collection and assign a specific StageName and CloseDate (same values) for every record in the Collection. I tried with a loop and assignment, but no luck, Is this also possible? Thank you
Yes, you are correct. Setting up hardcoded string in target data within Transform element is not possible as of now. I am sure Salesforce will bring that feature in future. Regarding your second point, it should be possible with look and assignment. I am not sure what error you are getting. You can even use Collecting Filter element also to filter out elements from collection (target data) and then use assignment to set StageName and CloseDate. Here is the video on Collection Filter: th-cam.com/video/jxOgWED5cYE/w-d-xo.html
Hey, thanks again for this demo. Can you help me with the error that I'm getting when I try this flow? It says "The "selectedRows[$EachItem]" field doesn't exist on the "flowruntime:datatable" object, or you don't have access to the field.".
Thanks so much for this - do you know if I can essentially display a data table of parent records and based on the selections use the transform element to create child records under the parent?
This is just one example. All you need to do select a record to fetch some information from that record and put it in child records to connect them through transform elements.
For the same use case in a record triggered flow, if you need to update all the contact records of the associated account based on some changes in account, is it possible? Since update record element requires an id to do the update, the transform element doesn’t return ID and hence update cannot be used as per my testing. Please correct me if I’m wrong.
Can you please create a video to transform source with nested collections received as output from HTTP callout and map it to target collection which will then be displayed on screen using data table
If we are using a transform element to convert opp to order, and then create the order, can we store the newly created orderId in the create record component itself?
Not going to lie but its absolutely frustrating to see that SF gives you so many ways to skin the cat ....we could just do this without Transform element too ....we could have also done it via Omnistudio.....We could have also done it via Trigger or Apex class...lolz
I absolutely agree. Giving so many options sometimes make things too complicated like which one to choose to make sure best practices are being followed. But I think between all these options. Trigger is code, Omnistudio needs additional license and flow is click/configuration option rather than customization.
The example in this video is fine for demoing the Transform feature, but I think the value added use-cases for Transform in the real world will be different. Like being able to transform a bunch of records from an external system that runs in a batch via a schedule-trigger flow. Could be the best-fit solution for organizations not needing a full featured EAI or iPaaS but still need to get some external data imported into Salesforce semi-regularly.
Thanks for this video. With this Transform element, can we create multiple records from Source to multiple records to Target? We have Master Opportunity and Child Opportunity. Each Master opportunity will have more than 1 opportunity line item and all the line items has to be created to all the child opportunities. I have the solution but with loop in a loop and DMLs with in the loop. How to tackle this situation? Help is much appreciated.
First really nice video. Second, in my use case I came accross, what seems to me, some limitations...can you please advise?
1. In the Transform element, let's say we want to set an hardcoded string in the target data, such as any StageName for Opportunities. Is this possible within the Trasnform element?
2. In the Transform element I'm using Opportunitis collections, where I mapped 4 or 5 fields. Now I want to iterate on the target data collection and assign a specific StageName and CloseDate (same values) for every record in the Collection. I tried with a loop and assignment, but no luck, Is this also possible?
Thank you
Yes, you are correct. Setting up hardcoded string in target data within Transform element is not possible as of now. I am sure Salesforce will bring that feature in future. Regarding your second point, it should be possible with look and assignment. I am not sure what error you are getting. You can even use Collecting Filter element also to filter out elements from collection (target data) and then use assignment to set StageName and CloseDate. Here is the video on Collection Filter: th-cam.com/video/jxOgWED5cYE/w-d-xo.html
Hey, thanks again for this demo. Can you help me with the error that I'm getting when I try this flow? It says "The "selectedRows[$EachItem]" field doesn't exist on the "flowruntime:datatable" object, or you don't have access to the field.".
I re-verified. It is working. I am sure you are missing some steps. Please make sure your profile has access to the fields. Thanks!!
Dude, very nice!
Thanks !!
Thanks so much for this - do you know if I can essentially display a data table of parent records and based on the selections use the transform element to create child records under the parent?
This is just one example. All you need to do select a record to fetch some information from that record and put it in child records to connect them through transform elements.
For the same use case in a record triggered flow, if you need to update all the contact records of the associated account based on some changes in account, is it possible? Since update record element requires an id to do the update, the transform element doesn’t return ID and hence update cannot be used as per my testing. Please correct me if I’m wrong.
Yes, you are correct.
Can you please create a video to transform source with nested collections received as output from HTTP callout and map it to target collection which will then be displayed on screen using data table
Thank you for providing the feedback and sharing the use case. Let me work on it. Will create a video soon.
If we are using a transform element to convert opp to order, and then create the order, can we store the newly created orderId in the create record component itself?
Yes you can
@@TechnicalPotpourri can you pls tell how?
Not going to lie but its absolutely frustrating to see that SF gives you so many ways to skin the cat ....we could just do this without Transform element too ....we could have also done it via Omnistudio.....We could have also done it via Trigger or Apex class...lolz
I absolutely agree. Giving so many options sometimes make things too complicated like which one to choose to make sure best practices are being followed. But I think between all these options. Trigger is code, Omnistudio needs additional license and flow is click/configuration option rather than customization.
The example in this video is fine for demoing the Transform feature, but I think the value added use-cases for Transform in the real world will be different. Like being able to transform a bunch of records from an external system that runs in a batch via a schedule-trigger flow. Could be the best-fit solution for organizations not needing a full featured EAI or iPaaS but still need to get some external data imported into Salesforce semi-regularly.