Skip to main content

[▶️]🔴🔥🎬 How to Configure Flow Transform Element | Spring24 New Flow Feature

The Transform element, a cornerstone of Flow Builder, has undergone notable refinements since its last iteration. One of the most compelling additions is the ability to seamlessly transform collections of data between flow resources. This enhancement unlocks a myriad of possibilities, allowing users to manipulate data with unprecedented flexibility and precision.

In this blog post and video, I am going to show you how you can aggregate data from a source collection to calculate the sum or count of items in that collection and assign the result to a target data field. You can also enter a fixed value for a target data field.  

📝 https://sudipta-deb.in/2024/03/how-to-configure-salesforce-flow-transform-element.html

🎬 https://youtu.be/_Rrb4aoG8Ek

 

@The Blog Group @* Release Readiness Trailblazers *

[▶️]🔴🔥🎬 How to Configure Flow Transform Element | Spring24 New Flow FeatureThe Transform element, a cornerstone of Flow Builder, has undergone notable refinements since its last iteration.

 

#New Releases #Release Updates Announcements #Release Readiness #Release Notes #Flow #Flows #Salesforce Flow #SalesforceTransformElement.jpeg

2 comentarios
  1. 25 sept 2024, 22:27

    It seems like this can, essentially, replace rollup summaries - the example starts with a record-triggered flow on a detail object, and updates a field with an aggregate value on a related record. But what about other types of aggregates? 

     

    For example, say I wanted to perform the same aggregate, but from a screen flow on my account. I would use a get records to get opportunities where Account.ID = $Record, and Stage = Closed Won. Then I would pass the resultant record collection into my Transform element, and I would want to total the Amount field of the Opportunities in my collection, then reference that value later in my flow (either to update a field in the Account record as in your example, or just reference within a Screen to show component A vs. B, etc.) 

     

    Is it not capable of this? Because I couldn't get it to work this way - the ability to define an Aggregate didn't even show up as an option in my Screen Flow, where my recordId = an Account, and my source record collection = Opportunities.

0/9000