Salesforce Winter 24 Release | Transform & Create Multiple Records in Salesforce Flow
ฝัง
- เผยแพร่เมื่อ 5 ส.ค. 2024
- Welcome to the Winter ’24 Release! Salesforce Release is the process by which Salesforce updates its software platform to add new features, enhancements, and bug fixes. Salesforce releases typically occur three times a year, in spring, summer, and winter, and are named after the season in which they are released.
In this video, I am going to share how you can transform collections of data between flow resources with the new Transform element in Flow Builder. I have a dedicated video where I have shown how to use this new element but in today's video, I am going to show you how to use this new element to transform and create multiple records within Salesforce Flow.
Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
▬ Contents of this video ▬▬▬▬▬▬▬▬▬▬
0:01 - Introduction
0:47 - Use Case Explanation
1:44 - Demo
8:55 - Conclusion
📌 Salesforce Winter 24 Release | Transform Your Data in Flows - • Salesforce Winter 24 R...
📌 Salesforce Winter 24 Release Playlist - bit.ly/3P0bun0
📌 Salesforce Summer 23 Release Playlist - bit.ly/3Mw6rbx
Display Custom Error Messages for Record Triggered Flows - bit.ly/3snudQv
📌 Salesforce Flow Playlist - bit.ly/3nIpTnT
📌 Rollback Records in Salesforce Flow - • Rollback Records in Sa...
📌 New Admin Features of Salesforce Summer '23 Release - • Salesforce Summer 23 R...
📌 New Flow Features of Salesforce Summer '23 Release - • New Flow Features of S...
📌 HTTP Post Call From Salesforce Flow - • Salesforce Summer 23 R...
📌 Summer 23 Release | How To Add Named Credentials To Permission Set Using Principals - • How To Add Named Crede...
📌 External Services in Flow - HTTP Callout - • External Services in F...
📌 Salesforce Release Playlist - bit.ly/3r7F0cn
📌 How To Secure Apex Code With User Mode Database Operations - • How To Secure Apex Cod...
#salesforce #winter24release #flow #errormessage #screenflow #transformdata #mapdata
✨ Blog: www.sudipta-deb.in/
✨ Subscribe for new videos on technology every week: bit.ly/3vCQKpg
✨Connect with me
📌 Twitter: / thesudiptadeb
📌 Website: www.sudipta-deb.in/
📌 LinkedIn: / sudiptadeb
📌 Facebook: / technicalpotpourri
Credit: Music I Use under the Mixkit License
Disclaimer: All opinions are my own and this video content is not endorsed by Salesforce, Google or any other company in any way. - วิทยาศาสตร์และเทคโนโลยี
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.
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!!
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.
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.
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
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.