Skip to main content

#Flows20 discussing

Hi everyone! 

 

I am trying to configure a new screenflow to have it's Uploaded File's name mapped into a text field.  I tried creating a Variable (Text-Collection) and added an Update Records element after the screen in an attempt to map it, but I can't get it right.   

 

What am I doing wrong here? 

 

Help with mapping attachment names into a field

 

image.png

 

image.png

 

 

 

 

 

#Flow  #Screen Flow  #Flows

12 answers
  1. Sep 8, 3:09 AM

    @Mario Santellan

      

    your flow is basically right — the only broken piece is the GetFileName filter value. In that resource picker you're currently on 'Related Record ID', which is the record you attached the files to, not the uploaded file. Instead pick the Upload File component's 'Content Document IDs' output (Upload File > Content Document IDs) — that's the list of the uploaded files' Ids. Also change the operator from Equals to In, since that output is a collection: the condition should read Content Document ID In → Upload File > Content Document IDs. Equals against a collection is exactly why nothing matched. Your Title mapping is already right — Title lives on the ContentDocument record, which is why 'Content Document from GetFileName > Title' works in AddAttachmentName (Title = file name without the extension; add FileExtension if you need the .pdf/.docx part). On multiples: with 'Only the first record' selected you'll capture just the first file's name. If a partner uploads 2+ files and you want them all, switch GetFileName to 'All records', add a Loop over it, and in an Assignment append each 'Loop > Title' (plus a comma) into a Text variable, then map that variable into File Name. If one name is enough, first-record is perfect as-is. Give that a try — it should populate.

0/9000

hello 

i can't access   this  suberbag   trailhead  page 

 

Advanced Flow for Agentforce Superbadge Trailhead page

tha,ks  for    help 

 

#Flows

4 answers
  1. Ajaypreet Singh Saini (Grantbook) Forum Ambassador
    Sep 8, 5:28 PM
0/9000

Hello, I would be interested in improving my Salesforce programmatic  and declarative skills by lending my services  pro bono (no money) . I have past experience 

working as a  Salesforce developer creating and maintaining automation for a couple of non-profit companies (Awana International and CBN) and would like to help lend my skills  and support in any way that I can.   Thanks much. 

 

#Nonprofit User Groups  #Salesforce Developer  #Flows

0/9000

A Flow calls an Invocable Apex method, and Apex updates the same record that triggered the Flow. 

Will the Flow run again?

  

 

#Flows

4 answers
  1. Sep 2, 12:25 PM

    No, the Flow itself won't automatically restart just because Apex updates the same record — Salesforce doesn't loop back into the currently running Flow from within its own transaction. 

    But watch out for this:

     

    If that Apex update happens to match the entry criteria of a

    Record-Triggered Flow (even the same one), Salesforce can fire a new Flow execution — because to the platform, it's just another DML update on the record, not "the same Flow running again." 

    One-line takeaway:

     

    Same Flow instance won't re-run recursively, but a fresh Flow trigger can fire on that DML — so it's still safer to add a guard condition (like checking if the specific field actually changed) if you want to avoid unintended re-entry. 

0/9000
4 answers
  1. Sep 2, 6:18 AM

    Hi @Archana Chittoor

    Yes, we can create a report to see the usage of Screen Flows.

    Go to Reports -> Public Folders -> Sample Flow Report: Screen Flow.

    This report shows:

    • Which users are running the Screen Flows
    • Number of flow executions
    • Flow interview status
    • Time users spend on each screen

    By default, the report shows data from the last 7 days. We can change the date filter, but the maximum available data is 31 days.

    If the report is not available, we can create a custom report type using Flow Interview Logs and Flow Interview Log Entries.

    Thanks. 

0/9000

Hello everyone, 

 

I want to learn flow from beginner to advance level, so can anyone pls tell me sequence of trails to learn flow in exact sequence. 

 

#Flow  #Flows

2 answers
0/9000

I have a Flow that needs to send an email when a record is created on a Custom Object.  No matter what I put in the recipient field, I continue to get "0 recipients Error ID: 1728011022-505532"when I try to trigger the flow.  

 

What I first tried was go search resources, triggering record -> Respondent field (this looks up the contact) ->Contact ID:

How to set Recipient ID in Flow Send Email Action

 

 

When that failed, I tried several different versions of creating a text variable to look up the same thing and put that in the recipient ID field.  Again, no luck.  Finally, I switched the look-up from "Search Resources" to "Enter Text" and put in the text of a contact ID I know for sure is active and has a valid email address, but still got the error. 

 

For this flow, I need to have it pull the email address of the Contact (Respondent) listed in these records.  What am I missing? 

 

 

#Flow  #Flows  #Custom Objects

3 answers
  1. Aug 25, 4:56 AM

    Hi, see the tool tip on the Recipient Addresses field which says it needs to have an email address not id. Try using the hardcoded email address and test to see its working.Hi, see the tool tip on the Recipient Addresses field which says it needs to have an email address not id. Try using the hardcoded email address and test to see its working.

0/9000

We are performing a migration from a legacy Salesforce Username-Password OAuth integration to an External Client App using Client Credentials. To validate migration behavior, we need the org-wide setting "Allow OAuth Username-Password Flows"

enabled in our org. Could Salesforce Support confirm whether this setting can be enabled, whether any feature flags are required, and whether there are edition-specific restrictions preventing its availability? 

 

#OAuth 2.0  #Usernames  #Password  #Flows  #External Application

2 answers
  1. Aug 19, 4:55 PM

    Hey Ramandra, 

     

    Himanshu's answer is accurate and matches what's actually being reported. Real-world evidence backs this up: even after explicitly turning on "Allow OAuth Username-Password Flows," users are still getting a "Username-Password Flow Disabled" error, confirming the toggle alone doesn't guarantee the flow will work, Salesforce's platform-level retirement enforcement can override it regardless of your org setting. 

     

    So to your three original questions: 

    - The setting existing and being toggleable doesn't mean the flow will actually function, this is confirmed behavior people are hitting even now 

    - Whether Support can override this for validation purposes is genuinely a case-by-case Support/AE conversation, not something the community can confirm 

    - Not edition-specific, it's the platform-wide retirement, not a licensing tier restriction 

     

    Practical suggestion: since you're already building the Client Credentials integration, validate it independently rather than trying to get the legacy flow re-enabled for a side-by-side. Compare against logs/behavior from your old integration instead of live-running both simultaneously, that avoids being blocked by something Salesforce is actively phasing out. 

     

    Reference:

    https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_oauth_username_password_flow.htm&language=en_US&type=5

0/9000

I have created 1 Orchestration Flow. It is breaking for 1 one of the Activity on the Connect Portal. 

If I am running the Orchestration Flow outside of the Connect Portal then it is working fine and giving me the respected output. 

I am working in 3-4 sandboxes but only on 1 sandbox it is giving me the following error.  

 

An Error Occurred with Your "Project Approval Flow" Orchestration

 

 

You’ve received this email because an error occurred while your "Project Approval Flow" orchestration was running. 

View debugging information for this orchestration in Flow Builder.

 

 

Error element Submit_for_Approval5 (FlowOrchestratedStage). 

An error occurred. Try again, or contact Salesforce Customer Support and provide this error ID: 53194206-372493 (1440708959)  

 

Can anyone help me with this. 

Is any permission or something is missing for the connect portal because of that it is not working. 

Need to find the solution asap. 

 

#Customer Service  #Flow-Orchestration

 

#Flows #Salesforce Developer #Architects

0/9000

 Global Medical Equipment Sales & Service Management Company MedTech Global manufactures and sells MRI machines, CT scanners, X-Ray equipment, and medical devices to hospitals worldwide. Departments: Sales Finance Service Logistics Legal Compliance Regional Managers Global VP Installation Team Support Team Objects Standard Account Opportunity Case Task Contract Asset User Quote Product Order Order Product Content Document Email Message Approval Custom Equipment_Request__c Installation__c Compliance_Check__c Finance_Approval__c Discount_Request__c Warranty__c Risk_Assessment__c Shipment__c Audit_Log__c Training_Request__c Service_Schedule__c Business Requirement Hospital submits an order for MRI Machine. Entire process must happen automatically. Step 1 Opportunity becomes Closed Won. Flow starts. Trigger After Save Decision 1 Order Amount IF Less than 100K Auto Approve IF 100K–500K Regional Manager Approval IF Above 500K Director Approval IF Above 1 Million VP Approval Decision 2 Discount % IF <10% No approval 10–20% Sales Manager 20–30% Finance Approval Above 30% CEO Approval Decision 3 Country IF USA Assign USA Team IF Canada Assign Canada Team IF Europe Assign EU Team IF Middle East Assign ME Team Else Global Team Decision 4 Customer Type Government ↓ Compliance Check Private Hospital ↓ Skip Compliance Research Institute ↓ Legal Review Decision 5 Equipment Type MRI ↓ Installation Team A CT Scan ↓ Installation Team B X-Ray ↓ Installation Team C Ultrasound ↓ Installation Team D Decision 6 Warranty Purchased? YES Create Warranty NO Skip Decision 7 AMC Purchased? YES Create Service Schedule NO Skip Decision 8 Training Required? YES Create Training Request Assign Trainer NO Skip Decision 9 Risk Score Low ↓ Proceed Medium ↓ Manager Review High ↓ Compliance Review Critical ↓ Legal Approval Decision 10 Inventory Available? YES Reserve Inventory NO Backorder Notify Procurement Get Records Customer Products Price Book Contract Previous Orders Open Cases Inventory Warranty Assets Service Team Loop Each Product MRI Monitor Battery UPS Printer Software License Training Kit For every product Create Order Product Asset Shipment Warranty Installation Task Collection Assignment Store All Tasks All Assets All Shipments Bulk Insert Create Records Order Order Products Shipment Tasks Installation Warranty Compliance Audit Training Finance Approval Update Records Opportunity Account Contract Assets Case Order Shipment Scheduled Path After 1 Hour Notify Warehouse After 24 Hours Check Shipment 48 Hours Reminder 72 Hours Escalation 7 Days Customer Follow-up 30 Days Customer Satisfaction Survey 365 Days AMC Renewal Reminder Email Notifications Sales Rep Finance Warehouse Customer Regional Manager VP Compliance Training Team Support Installation Team Custom Notification Salesforce Bell Notification Approval Required Shipment Delayed Installation Assigned Training Scheduled Payment Pending Subflows Discount Approval Compliance Check Warranty Creation Training Shipment Audit Log Customer Notification Risk Assessment Validation Rules Cannot Close Opportunity If Primary Contact Missing Cannot Submit If Hospital License Missing Cannot Approve If Discount >40% Without CEO Cannot Ship If Payment Pending Cannot Install If Compliance Pending Duplicate Rules Prevent Duplicate Hospital Duplicate Equipment Request Duplicate Warranty Duplicate Installation Record Locking During Approval Opportunity Order Contract Become Read Only Platform Events Payment Received Shipment Completed Equipment Installed Warranty Activated Invoice Generated Subscribers ERP SAP Finance Warehouse Fault Paths If Order Creation Failed ↓ Create Audit Log ↓ Email Admin ↓ Retry Queue Security OWD Opportunity Private Role Hierarchy Sales Rep ↓ Sales Manager ↓ Regional Director ↓ VP Sharing Rules Finance Can Read Orders Warehouse Can Edit Shipment Support Read Assets Legal Read Compliance Permission Sets Finance Approval Shipment Manager Warranty Team Compliance Team Field-Level Security Hide Discount Cost Price Margin Fraud Score Salary Restriction Rules Sales Rep Only Region Records Finance Only Approved Orders Warehouse Only Pending Shipments Formula Fields Profit % Margin Warranty Remaining Delivery SLA Expected Installation Date Risk Category Approval Process Opportunity ↓ Sales Manager ↓ Finance ↓ Compliance ↓ Director ↓ VP ↓ Approved Reports Orders Pending Approval Pending Shipment Delay Installation Due Warranty Expiry Training Pending High Discount High Risk Open Compliance Dashboard Daily Orders Monthly Revenue Average Approval Time Pending Shipment Top Sales Rep Delayed Installations Risk Heat Map Integration SAP ERP Payment Gateway DocuSign ServiceNow Marketing Cloud Slack Microsoft Teams MuleSoft  

 

#Flow  #Flows  #Salesforce Admin

1 answer
  1. Aug 5, 4:33 PM

    Hey Rohit, 

     

    This is a massive scenario — basically a full enterprise Service/Sales Cloud implementation compressed into one post, not something buildable as a single Flow. If you're using this for practice/interview prep, here's how I'd break it into buildable phases rather than trying to tackle it as one build: 

     

    1. Core Order Flow (the actual automation) 

    One Record-Triggered Flow on Opportunity (After Save, Closed Won) handling Decisions 1–10 in sequence. Given the branching complexity (10 decision points), structure this as a master Flow calling Subflows for each major decision block (Discount Approval, Compliance Check, Risk Assessment, etc.) — a single flat Flow with this many branches becomes unmaintainable fast. 

     

    2. Approvals — don't build all of this in Flow 

    Decisions 1 and 2 (amount-based and discount-based approval tiers) map much better to native Approval Processes with multi-step approval chains than to Flow-managed approval logic. Use Flow only to Submit for Approval and react to the outcome. 

     

    3. The product loop (bulk-safe) 

    Loop through products → build collections for Order Product, Asset, Shipment, Warranty, Installation Task → bulk-insert each collection once, outside the loop. This is the part most likely to hit governor limits if built carelessly (DML inside the loop instead of collections). 

     

    4. Scheduled Paths 

    Each of your time-based followups (1hr, 24hr, 48hr, 72hr, 7-day, 30-day, 365-day) is a separate Scheduled Path off the same Flow or a dedicated time-based Flow — don't try to chain these off one one Scheduled Path. 

     

    5. Everything else is configuration, not Flow 

    Sharing rules, OWD, Role Hierarchy, Permission Sets, Field-Level Security, Duplicate Rules, Validation Rules — all pure declarative setup, unrelated to the Flow itself. Build these first since the Flow's record access depends on them being correct. 

     

    6. Platform Events / SAP integration 

    These are outbound publish points from your Create Records steps (Payment Received, Shipment Completed, etc.) — straightforward Platform Event Publish actions in Flow, but the actual SAP/ERP consumption side is outside Salesforce's scope. 

     

    Given the size, I'd start with just Decisions 1–3 (approval tier, discount tier, region assignment) as a working end-to-end Flow first, then layer in the rest incrementally. Trying to build all 10 decisions + loop + scheduled paths + subflows in one pass is where this kind of build usually falls apart. 

     

    What are you actually trying to do with this — build it out as practice, or is this a real client requirement you're scoping?

0/9000