Skip to main content

#Flow토론 중인 항목 132개

댓글 4개

I'm looking for support troubleshooting a record triggered flow that creates records when a lead is converted. When the lead is converted it gets related campaign members and should create records of our custom object, Event Contact Role (ECR). In the flow, the campaign members are added to a record collection (ECR_FromLead). To prevent duplicate ECR's, 1) it gets existing ECR's with the converted contact Id and stores them in a record collection (ECR_Exists), 2) filters existing ECR's from those from the lead. The remaining ECR's from ECR_FromLead are adding to a final record collection ECR_ToCreate.  

 

Event Contact Roles have a lookup to Events. My filter loop loops through the collection ECR_FromLead. The filter action collection is ECR_Exists and filters on loop item Event Ids that does not equal the Event Id of those that exist. The remaining ECR's that don't equal the existing get added to the ECR_ToCreate collection. 

 

When I test converting a lead the flow doesn't seem to fail but no ECR records are created. I can't test my flow in debug because I can't convert a lead. I want to try changing my trigger by I don't know how that would still give me the Converted Contact Id to test parts of the flow. 

 

Thanks in advance! 

Converted Lead & Campaign Member

 

 

LeadEcrFlow2.png

 

 

LeadEcrFlow3.png

 

 

LeadEcrFlow4.png

 

 

 

#Flow  #Lead Conversion

답변 1개
  1. 10월 30일 오전 7:01

    Bug: Your != filter is the problem.👇🏼

    When there are no existing ECRs, the filtered collection is empty, so nothing ever gets added to ECR_ToCreate — that's why the flow runs without failing but creates nothing. With multiple existing ECRs it also breaks the other way: one different Event makes the filter non-empty, so duplicates slip through.

    Fix — replace the filter with a contains check:

    1. Create a Text Collection variable: Existing_Event_Ids
    2. Loop through ECR_Exists once, add each record's Event Id to Existing_Event_Ids
    3. Loop through ECR_FromLead, with a Decision:
      • If Existing_Event_Ids contains the loop item's Event Id → do nothing, skip it
      • If not → add the loop item to ECR_ToCreate, and add its Event Id to Existing_Event_Ids (this also stops duplicates within the same conversion)
    4. After the loop, only Create Records if ECR_ToCreate is not empty

    For testing: move steps 2-4 into a Subflow that takes Contact Id as input. You can debug the Subflow directly with a Contact Id, without converting a lead. 

Hey there, I am doing an implementation for my client who requires service reports to be generated for their Work Order Line Items on a regular basis.

 

I have created a daily scheduled Flow that finds all completed Work Order Line Items for that day and loops through each record to create Service Report records for each of those WOLIs.

 

I am running the flow as a System Administrator user and it works fine when I debug it, but when I activate the schedule triggered flow I get the following error: "INSUFFICIENT_ACCESS_OR_READONLY: null. You can look up ExceptionCode values in the SOAP API Developer Guide.---This error occurred when the flow tried to create records:"

 

I can't access the Sharing Settings for Service Reports or Work Order Line Items but the user running the flow (who is the same as the Default Workflow User in the Process Automation Settings) is System Admin with ability to View and Modify all data in the environment.

 

Any ideas? Thanks in advance! 

답변 5개
  1. 10월 29일 오후 2:40

    Hi Camille, thank you so much for taking the time to share your experience and suggestions. Your description sounds very similar to what we’re seeing: the Service Report is created successfully during manual or debug runs, but fails when the Work Order is updated by the scheduled flow.

    I’ve opened a case with Salesforce Support to get a concrete explanation of why the Service Report creation fails specifically in the scheduled-flow context. They shared the documented Apex approach for creating a Service Report, and I’m following up with them to confirm whether that will work for our setup and what is causing the current failure.

    Your suggestion to move report creation out of the scheduled flow is very helpful. We’re also making sure any solution will prevent a Work Order from being marked Closed if its Service Report isn’t successfully created.

    Thanks again for sharing what worked for your team!

I have a requirement to build data capture flow for partner community users. The flow is launching from a quick action. It will contain a screen component "Upload image". This is working in FSL mobile app.  but it is not working in community portal. Do you have any solution?  

Data Capture Image upload not working in partner community portal

 

 

 

#Flow  #Salesforce Flow

답변 6개
  1. 10월 29일 오후 1:56

    Hi guys,  

     

    I can't upload images in the FSL mobile app using a Data Capture Flow.  

    Hi guys, I can't upload images in the FSL mobile app using a Data Capture Flow. Can someone please help?image.png

     

    Can someone please help? 

     

    Thanks, 

    Mo

A Record-Triggered Flow updates related records whenever an Opportunity is modified, even when unrelated fields change. How would you optimize the Flow using entry conditions, decision elements, and execution settings to improve performance and avoid unnecessary updates? 

#Trailhead Challenges #Flow

답변 3개
  1. 10월 14일 오후 4:03

    Hi @Durga Prasad Karnaty I would first check why the Flow is running on every Opportunity update.

    A few things I would suggest:

    1. Entry Conditions: Run the Flow only when required conditions are met.
    2. Run Settings: Use "Only when a record is updated to meet the condition requirements" where applicable.
    3. Check Field Changes: Compare $Record and $Record__Prior to identify changes.
    4. Decision Element: Continue only when relevant fields have changed.
    5. Avoid Unnecessary Updates: Update related records only when needed.

    Best Practice: Filter records early and avoid unnecessary DML operations to improve Flow performance.

    Hope this helps!

답변 1개
  1. Eric Burté (DEVOTEAM) Forum Ambassador
    10월 24일 오후 10:03

    Hello @Eduardo Vitor, make sure you have well saved and activated the last version of your flow. Try to insert again your resource in the display text if you keep facing the issue. Because, that should work like below :Hello , make sure you have well saved and activated the last version of your flow. Try to insert again your resource in the display text if you keep facing the issue.Based on this display textimage.pngEric

When either setting up an Email Alert, Salesforce will not make my org's default no-reply email address as an option.     On an Email Action within Flow, Salesforce will not let you Save a flow if the sender is the default no-reply email address.    Why can't I select my no-reply email address as a sender within an Email Alert or Flow?   

답변 9개
댓글 7개
댓글 3개

Hi everyone! I have a Salesforce Flow that sends confirmation emails. My Email Alert, Org-Wide Email Address, and email settings are configured correctly, but email delivery is intermittent: sometimes emails arrive, sometimes they don't.

I checked the Salesforce Email Logs, and failed messages show a DKIM authentication error (550-5.7.30).

Has anyone experienced this issue? How can I fix it? I appreciate your help. 

I appreciate your help! Thank you! 

 

#Flow  #Email Deliverbility

답변 4개
  1. 10월 19일 오후 2:44

    Hi @Ariana Bayona,  

    Why it’s intermittent: If your Org-Wide Email Address is a Gmail or Yahoo address, Gmail’s DMARC policy tells receiving servers to reject mail with an @gmail.com From address that doesn’t come from Google’s own mail servers. Mail from Salesforce can’t be DKIM-signed for a domain you don’t own, so it gets through at some receivers and is rejected at others. A verified org-wide address only proves you own the mailbox. It doesn’t authenticate the domain. sage

    Options without buying a domain:

    1. Use the substitute-address setting (best free fix). In Setup > Deliverability, enable “Use a substitute email address for unverified domains.” Salesforce then sends from a technical address in the form email@UniqueId.sfcustomeremail.com, using its own verified domain. Keep your real address as the Reply-To so replies still reach you. Check the exact setting name and location in your org. I haven’t confirmed where it sits in the current UI. salesforcebreak
    2. Send From a domain you already have access to. If you can use an address on a work or school domain, ask whoever manages that domain’s DNS to set up a DKIM key (Setup > DKIM Keys) or add it as an Authorized Email Domain.
    3. Buy a cheap domain. It’s roughly $10/year. Both DKIM keys and Authorized Email Domains require a domain you can add DNS records to, so there’s no free route to full authentication.

    Check first: Open the failed messages in Email Logs and confirm which From address was used. Salesforce also now requires verified sending domains (from Spring ‘26, emails must come from a domain verified as belonging to your organization), so if your From is a free-mail address, this change could be part of why delivery became unreliable. If your From is not a free-mail address, tell me what it is and I’ll rework the diagnosis. salesforceben

    Sources:

    I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.