Hi @Yeshwanth Macha ,
Try launching a new playground. I was able to resolve this issue by doing so, as others have suggested.
However, I ran into a different issue with a subsequent step, the Get 1500 Product, which required Salesforce's help. The "All Conditions Are Met (AND)" condition requirement wasn't working correctly. Hopefully it is for you. When you Edit Get Records for the "Get 1500 Product" and "Get 2000 Product," manually type the simple numerical values "1500" and "2000" in the respective values field. Do not select the "X1500kW" or "X2000kW" values that appear when you start typing.
https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007A2YKXSA3
#Salesforce Flow0 personne en discute
- Activité récente
- Date de création
- Recommandé
- Toutes les questions
- Questions avec une réponse acceptée
- Questions sans réponse
- Questions sans réponse acceptée
[▶️]🔴🔥🎬 SECRET to NO CODE Visual Progress Indicators in Salesforce Flow!
In this video, I will be sharing how to implement a visual progress indicator in Salesforce Flow without writing any custom code, just by doing some configurations.
▬ Contents of this video ▬▬▬▬▬▬▬▬▬▬
0:01 - Introduction
0:43 - Implement the basic use case
4:26 - Implement the complex use case
9:45 - Use the variable Flow ActiveStages
11:26 - Use the variable Flow CurrentStage
12:06 - Activate this feature in older flows
12:44 - Final Thoughts
@The Blog Group @* Release Readiness Trailblazers *
#Flow #Salesforce Flow #Flownatics #New Releases #Release Readiness
I have a screen flow that (sometimes) uses a picklist (component is displayed conditionally)
The picklist is populated from a template depending on which template keyword is entered in the screenflow. The fields that populate the picklist are up to 6 text fields in the template. How do I restrict them from showing up in the screenflow picklist if they are null?
On the templates that do use the picklist, there could be anywhere from 1 to 6 fields that populate the picklist, however if there are less than 6 fields populated, it still is displaying the null values in the picklist, so a user could conceivably select a null value from the list which obviously is not desired.
How do I restrict the picklist to only the fields that are not null in the source template?
#Flow #Flows #Salesforce Flow @Salesforce Flow Automation #Validation Rule For Picklist On Picklist
12 nov. 2024, 18:12 If I understand the use case, I think you can get what you need using the Quick Choice component from Unofficial SF. I set the values (or left the text box blank) in the first screen. Then, I added each answer to a Text Collection variable in the Assignment element. Next, I loop through the values in the Collection variable to see if they are blank. If so, I remove the value from the Collection. Then, using the Quick Choice component, you can display the remaining values from the string in the following screen:
Hi, is there way to share files attached to a case by internal users with community users who have access to the case record automatically. I am trying to explore declarative options available before opting to write code. #Experience Cloud #Salesforce Admin #Salesforce Flow
Forum Ambassador Tom Bassett (Vera Solutions)
2 nov. 2023, 16:57 This describes the different options here for File Access in Experience Cloud
https://help.salesforce.com/s/articleView?id=sf.networks_files_visibility_and_sharing.htm&type=5
Are files already set to Controlled by Record Access?
Hello!
I would like to build a flow with the following parameters:
When Account Liaison Working = True and Account Liaison Completed = False and it's been six days since Account Liaison Working = True send an email to User who marked Account Liaison Working = True.
Is this possible?
Thanks in advance
22 oct. 2024, 22:29 It is possible. Steps -
- Trigger: When Account_Liaison_Working__c = True and Account_Liaison_Completed__c = False.
- Scheduled Path: Wait 6 days after Account_Liaison_Working__c is set to True.
- Decision: After 6 days, check if Account_Liaison_Working__c = True and Account_Liaison_Completed__c = False.
- Action: If both conditions are still true, send an email to the user who marked the field.
Greetings Everyone, I'm a fresher looking to start my career as a Salesforce Developer. Had no experience with Salesforce, So wanted advice about what will be the best path for me to start my journey of becoming a successful Salesforce Developer. Where should I began with which modules should I pick up as I have no prior knowledge about Salesforce.
#Salesforce Developer #Flow #India #Ask An Expert #Salesforce Flow
[▶️]🔴🔥🎬 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 *
#New Releases #Release Updates Announcements #Release Readiness #Release Notes #Flow #Flows #Salesforce Flow #Salesforce
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.
Hi All,
I need a way to remove duplicates from a Collection Variable without writing code.
My Flow processing gets me to a point where I have a Collection Variable that contains ContactIDs for Contacts that I will send an email to. Here is what the contents of the Collection Variable looks like.
ContactID Collection Variable: ContactID1, ContactID2, ContactID3, ContactID4, ContactID4, ContactID4
My challenge is ContactID4 is replicated 3 times within my Collection Variable. If I send an email to the Contacts in my Collection Variable then ContactID4 will get 3 emails.
How can I de-dupe my Collection Variable so ContactID4 only occurs once?
Thanks!
Chris Hoffart
Mobile Loaves & Fishes
Forum Ambassador Davis Johnson (SolomonEdwards)
13 nov. 2023, 15:00 Yea I think I glanced over that from the original use case.. the remove uncommon operator likely won't be of much help here. Either doing what Eric recommended or unpacking the collection after the insertion (loop it, decision element checking its presence in a new collection, if found=>skip to next, if not found=>insert into new collection) would likely both work just fine.
I'm creating a flow that should send an email to a contact based on certain criteria, but it isn't working. I added the contact's ID in the Recipient ID field, but it says that an 'Error Occurred: 0 recipients' when I debug.
I've attached a screenshot below. What am I doing wrong?
[▶️]🔴🔥🎬 How to Pre-populate Flow Repeater Component with Data Collection | Winter ’25 Release
In this blog post and youtube video, I will be sharing improved Flow Repeater Component. After Winter 25 release, if you have the collection of data available, then this repeater component can work on pre-populating the inside screen component with collection data automatically.
This Flow Repeater Component will provide 4 outputs to deal with different scenarios. They are –
📌 All Items – This collection will contain all the pre-populated items and also the newly added items.
📌 Added Items – This collection will only contain newly added items.
📌 Prepopulated Items – This collection will only contain prepopulated items.
📌 Removed Items – This collection will only contain removed items.
🎬 https://youtu.be/N-Waq7LzTqY
📒 https://sudipta-deb.in/2024/08/flow-repeater-element-to-pre-populate-data-winter-25-release.html
@The Blog Group @* Release Readiness Trailblazers *
#Flow #Screen Flow #Salesforce Flow #Salesforce Developer #Salesforce Admin #New Releases #Release Readiness #Release Updates Announcements