#Flow토론 중인 항목 155개

I have a requirement to build a Flow that will send out a series of emails to Lead prospects based on the Lead Source. Each Lead Source has it's own unique set of emails that will be sent out on a timeline. There are 4 total Lead Sources that will have a series of emails sent out. Each Lead Source will get the following schedule of emails: 

Immediately after creation of Lead, 2 Days after, 4 Days after, 7 Days after, 10 Days after, 30 Days after, 60 Days after, 90 Days after, 120 Days after, 150 Days after, 180 Days after, 210 Days after, 240 Days after, 270 Days after, 300 Days after, 330 Days after, and 360 Days after Lead creation. 

So that would be 17 different scheduled paths and there are 4 Lead Sources so that would make a total of 68 email possibilities. 

What would make the most since in a design for this Flow structure. I could use Decision elements after each Scheduled Path and have email alerts. Doing so would make a large Flow. What would be a better solution is designing this type of Flow? 

Hi Tableau Community! I am looking to create a License Matrix for my org. We are currently going through a merger and acquisition, and we want to do an inventory of both environments.  

I have data prepped through Tableau Prep. Attached Excel file is the dummy data of the Output. 

I have also attached the Tableau .twbx of a WIP file.

Below is the License Matrix we want to create (numbers are not accurate. This is just a mock of what we want to recreate).

Much appreciate the help! Any tips would be great. Please note I can use Tableau Prep to massage the data if required. 

I have a screen flow on a campaign page that a user can run to tag all related opportunities (Donations actually, this is NPSP) for further processing, which will be thank-you letters in Apsona. It basically just un-checks a checkbox on all donation records that are checked from last time, then checks the same checkbox for all donations related to the current campaign. 

I have an on-update flow that normally runs when a donation record is updated, but I DON'T want it to run when that screen flow causes all those updates. 

When the number of donations gets too large, I end up with

errors. 

Any thoughts? Thank you!

I have a flow that creates a Conversion Event record (custom object) whenever a Campaign Line (CLN) record (related custom object) is created (via the Clone button). Typically, there are multiple Conversion Events, which are auto-numbered, related to a CLN. The intention of the flow is to clone/copy over those Conversion Events from the old CLN to the new cloned CLN without the user having to recreate them.  

In the flow, I use a Get Records to pull all the Conversion Event info from the previous CLNs and then loop through all the records and use an Assignment to assign the values to the field variables and a Collection to hold all of the newly created records. However, I have one field, a picklist that is just a list of numbers 1-20, that doesn't always pull the number from the looped records and populate in the new Conversion Event record. 

Does anyone know why this would happen and how it can be fixed? I'm wondering if there is something nuanced about using numbers in a picklist that I don't know about? 

Thanks! 

Hello! 

I want to create a flow that launches a case, but only on a quarterly basis.  I am not seeing where I can do that in the flow. 

BB 

For a Template-Triggered Prompt Flow using the 'Service Email Summary Template Capability,' the only input available is plain Email Content text — no Case ID or record reference. Is there any way to also pass in a Case record or its fields with this specific flow type and capability, or is that a hard limitation?

#Trailhead Support  #Flow  #Prompt Builder  #Einstein For Service

I'm working on a Flow that needs to update a large batch of related records (a few thousand) triggered from a record update on the parent object. I've read that Record-Triggered Flows can run into governor limits or performance issues at scale, and I'm trying to figure out the right pattern before I build this out further.

For those who've dealt with bulk updates like this — is it better to handle this with a Scheduled Flow / batch approach instead of a real-time Record-Triggered Flow, or is there a cleaner declarative pattern I'm missing? Trying to avoid needing an Apex trigger if possible, but open to it if that's genuinely the better path here. 

#Flow  #Automation@Salesforce Flow Automation