#Flows34 personnes en discutent

 Hii Lisa,

The 1–20 picklist values are not the issue. I would check the Flow’s loop or assignment

pattern first.

Make sure the picklist is assigned directly from Current Item from Loop to the new record variable, then add that record variable to the collection. Create the records after the loop, not inside it. Salesforce specifically recommends this pattern because the Current Item is reset on each iteration.

Also verify that the picklist values are "Active" and available for the target "Record Type"

 (and controlling value, if it’s dependent). 

Check this for references: 

 https://trailhead.salesforce.com/content/learn/modules/loops-in-flow-builder/build-a-loop

https://help.salesforce.com/s/articleView?id=platform.troubleshoot_picklist_values.htm&type=5

Hi @James K.k

The biggest win is usually reducing database operations, not just reducing Flow elements.

I’d bulkify the Flow around collections, eliminate Get Records/DML inside loops, and query only the fields/records actually needed. If the volume or logic still pushes governor limits, I’d move that part to Apex and let Flow handle the orchestration.

Hi @Stephanie Huffman

Yes, you can use a Record-Triggered Flow on Opportunity to assign the Price Book. Trigger it when the Opportunity is created or its Account changes. Use Get Records to find the Price Book related to the Account, then update the Opportunity’s `Pricebook2Id`. If multiple Price Books are used, store the Account-to-Price Book mapping in a custom field or object. This will automatically assign the correct Price Book. 

If this answer is Helpful for You Please Mark as Best Answer. 

Hi @Deepak Sachdeva

, 

Thank you for the suggestion. I tried that, exactly as you laid out, but it still did not work.  

I am happy to announce, however, that I spoke with Salesforce support on Friday and they did get it to work. Confusingly, it was one of the options I had tried before, which is in the list of my original post.  

This is the URL that worked:  

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id

}&retURL=/lightning/r/Opportunity/{!OpportunityLineItem.Opportunity_Id__c}/related/OpportunityLineItems/view 

Hello Amit, 

Yes, this can happen due to backend synchronization/caching. Newly created Flows may take a few minutes before they become available in the Reference Action dropdown for a subagent. It’s not usually an issue with the Flow itself. There doesn’t seem to be a fixed guaranteed propagation time, but in practice, waiting a few minutes and refreshing/reopening the action configuration usually makes the Flow appear. Hope this helps!

@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.

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

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.