Skip to main content

#Flownatics0 discussing

Trailblazers, we’re cleaning up the automation roadmap and we have one goal: Make your life easier. Forget the "corporate" wish list. We want the raw, unfiltered truth from the people actually in the trenches. What’s working? What’s frustrating? What’s missing?

  • Time: 5 minutes.
  • Impact: Direct line to Product & Design.
  • Result: You help decide what we focus on next.

Fix Flow Link Here!

 

Thank you for your time and consideration :) 

 

#Flownatics #Automation #Salesforce Admin #Admin #Salesforce Developer

2 comments
0/9000

💬 We’re back on September 16 with the next True to the Core Deep Dive, and this one is for the #Flownatics!💬 We’re back on September 16 with the next True to the Core Deep Dive, and this one is for the !Based on feedback from our first episode survey, we’re focusing on testing and debugging in Flow.

Based on feedback from our first episode survey, we’re focusing on testing and debugging in Flow. 

Join Salesforce Product Managers @Sam Reynard, @Adam White, and @Henry Liu as they: 

 

✅ Walk through recently delivered ideas 

✅ Showcase new capabilities to test and troubleshoot flows 

✅ Share the roadmap for what’s coming next 

 

We’ll wrap up with a live Q&A so you can ask your questions directly to the product team. FYI, the event countdown will begin at 8:50 a.m. PT, but the event itself will run from 9-10 a.m. PT.   

 

➡️ RSVP here to get a reminder to watch. ⬅️ 

➡️ Want to learn more about this series? Check out this blog post. ⬅️ 

 

#True To The Core #IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects

 

@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Architect Trailblazers, @TDX for Admins, @* Salesforce Developers *

8 comments
0/9000

I'm working on the third version I have of a Flow that creates related records from an Interaction. My first version just created the related records from a list that is created dynamically. The second version allows Users to pick and choose which of those records are being created. In this third version, I want to eliminate the ability to create records, if they currently exist.  

 

I've added this loop to go through the list  that creates the new records, to see if there are records associated with members of that list. I've even asked AI (which I was trying not to do), and every suggestion it gave, I have correct, or have corrected.   

Deduping Record Creation from a flow

 

I can obviously expound on any questions on elements in use, but can anyone see where this may be going wrong?   

 

#Flownatics @Salesforce Flow Automation #Salesforce Developer #Architects

3 answers
  1. Mar 8, 4:55 PM

    Looking at your Flow deduplication logic, I can see a few potential issues that might be causing problems. Let me help you troubleshoot this.

    Common Issues with Flow Deduplication Patterns

    1. Get Records Element Configuration

    The most common issue is how the Get Records element filters against your collection. When checking if records exist, ensure:

    • Filter Logic: Your Get Records should filter where a field (like a lookup or external ID) equals {!loopVariable.SomeIdentifier}
    • Store Output: Make sure "Automatically store all fields" is selected, or explicitly select the fields you need
    • How Many Records: Set to "All records" if you expect multiple matches, or "Only the first record" if checking for existence

    2. Decision Element Logic

    After your Get Records, your Decision should check:

    • Condition: {!GetRecordsVariable} Is Null = {!$GlobalConstant.True} (record doesn't exist, safe to create)
    • OR: Check if the collection from Get Records has a count of 0

    3. Loop Variable Reference

    Make sure you're correctly referencing the current item in your loop when filtering the Get Records. The syntax should be:

    • {!currentItemFromLoop.FieldName} not just {!FieldName}

    Recommended Pattern

    Here's the typical deduplication flow structure:

    HTML

     

    1. Loop through your collection

    2. Get Records (filter by unique identifier from current loop item)

    3. Decision: Does record exist?

    - If No → Add to "Records to Create" collection

    - If Yes → Skip (or add to "Records to Update" collection)

    4. After loop completes → Create Records (using "Records to Create" collection)

    Specific Things to Check

    Without seeing your exact configuration, here are the most likely culprits:

    In your Get Records element:

    • Are you filtering on the correct unique field (External ID, lookup, or combination)?
    • Is the filter comparing against the current loop item's field value?
    • Did you set "When no records are returned" to "Put null in the variable"?

    In your Decision element:

    • Are you checking if the Get Records variable Is Null (meaning no match found)?
    • Or checking if a collection variable's count equals 0?

    In your Assignment/Collection:

    • Are you adding the current loop item to a new collection only when the Decision confirms no duplicate exists?

    Best Practice Alternative

    Consider using upsert logic instead of pure deduplication:

    • Use an External ID field on your target object
    • Populate that External ID in your source collection
    • Use Create Records with "Use separate resources for each record" and let Salesforce handle the upsert
0/9000

💻 True to the Core Deep Dive: Flow and Automation Recap

 

Thank you to everyone who joined True to the Core Deep Dive today, and to Salesforce product leaders @Sam Reynard, @Rubin Roy, @Kel Wetherbee, and @Adam White for sharing updates and answering all your great questions.  

 

🎥 Missed the session? 

You can watch the full episode on demand here.  

💻 True to the Core Deep Dive: Flow and Automation Recap Thank you to everyone who joined True to the Core Deep Dive today, and to Salesforce product leaders , , , and for sharing updates and answerin

 💬 Still have questions? 

Drop them in the comments below. We’ll do our best to get you answers!  

 

📝 Shape future TTTC Deep Dive topics! 

Please take a moment to fill out this quick survey about the session and help shape future session topics. 

 

🔗 Resources shared during the session: 

● Admin Blog: Flow Orchestration Is Now a Standard Flow Type: No Add-On Required

● Admin Blog: Spring '26: Design Screen Flows With Intent Using Styling Overrides

● Admin Blog: Inside Dreamforce '25: Salesforce Platform Sneak Peeks for Admins

● True to the Core Deep Dive: Flow Testing and Debugging Session 

 

Stay tuned for updates on next month's session! We can't wait for you to join us again.  

  

#True To The Core @IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects

 

@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Trailblazer Community Cove, @Admin Addicts, @* Salesforce Developers *@TDX for Admins, @Architect Trailblazers #Automation #Flownatics

2 comments
0/9000

💬 Have a question about Flow? Bring it to our next True to the Core Deep Dive on February 24. 

 

Join @Sam Reynard, @Rubin Roy, @Kel Wetherbee, and @Adam White from the Flow product team for a Q&A-focused conversation on Flow and automation.  

 

Here’s what you can expect: 

💬 Open Q&A with the Flow product team 

🔀 Practical guidance on Flow and automation 

💡 Insight into what's new and what's coming next 

⚡ A chance to share feedback  

 

If Flow is part of your day-to-day work, or if you’ve been looking for a chance to ask questions directly to the team building it, we’d love to have you join. 

 

➡️ RSVP here. ⬅️💬 Have a question about Flow? Bring it to our next True to the Core Deep Dive on February 24. Join , , , and from the Flow product team for a Q&A-focused conversation on Flow and automation. #True To The Core @IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects

 

@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Trailblazer Community Cove, @Admin Addicts, @* Salesforce Developers *@TDX for Admins, @Architect Trailblazers #Automation #Flownatics

5 comments
0/9000

🥁 Introducing - The FLOWERS Framework for Salesforce Flows 🌸 

Salesforce Flow has become the core automation engine of the platform and it's incredibly powerful. 😎  

 

But let's be honest… with great power comes a lot of tangled logic, inconsistent design decisions, and automation that is hard to scale or maintain 😅 

 

That's why I am excited to share the enhanced "FLOWERS" Framework - a memorable and practical approach for designing scalable, secure, optimized, and well-governed Salesforce Flows. 

 

The FLOWERS Framework is built to help teams, 

🌟 Standardize automation design 

🌟 Improve maintainability 

🌟 Strengthen security & compliance 

🌟 Enhance performance 

🌟 Reduce technical debt 

🌟 Build with confidence 

 

This framework is based on my learnings and experiences working with Flow and it will continue to evolve as the platform grows and new features roll out. 🌱 

 

If you have seen patterns, best practices, or pitfalls I missed, I would love to hear them. 😁  

 

Drop your suggestions or improvements in the comments so we can continue refining this together as a community. 👇 

 

LinkedIn Newsletter - 

https://www.linkedin.com/pulse/flowers-framework-salesforce-flows-logesh-matheswaran-ruvoc

 

🥁 Introducing - The FLOWERS Framework for Salesforce Flows 🌸 Salesforce Flow has become the core automation engine of the platform and it's incredibly powerful.

 

#Flow  #Flownatics  #Salesforce Admin

6 comments
  1. Jan 15, 6:44 AM

    @Neppoliyan Rajaram

    This framework is not part of the Winter ’26 release. It’s an independent framework that I created. 

     

    @Dimitar Nikolov You can find it here

     

    @Andy Engin Utkan

    Thanks. Sure, will think about it. 

     

    @Daryl Moon

    To answer to your question 

     

    1. The naming conventions provided in the article are

    illustrative examples

    , not mandatory rules. Every organization has its own established naming standards, and these examples can be adapted accordingly. The same applies to Subflow naming conventions. 

    2.  KISS applies to usage, not to the absence of conventions. 

     

     

0/9000

🚀 Sort and Edit in Flow Data Table component | Save Changes within Flow 🚀

 

 

In this quick tutorial, I'll show you exactly how to use the new features of the data table component from Salesforce's Spring 26 release. Learn how to implement inline editing and column sorting directly within your screenflow, making your workflow automation more efficient. This update offers significant enhancements for any Salesforce developer working with Flow Builder. 

 

Also, I have shown how to save the inline edit changes properly in Salesforce.

 

📺 Watch the full video here: https://youtu.be/n_YgSPdj1no

 

 

#Salesforce Developer #Salesforce Admin #Flow #Flownatics #FlowBuilder #New Releases

 

@The Blog Group @* Release Readiness Trailblazers *

   

🚀 Sort and Edit in Flow Data Table component | Save Changes within Flow 🚀 In this quick tutorial, I'll show you exactly how to use the new features of the data table component from Salesforce's Spri

 

 

0/9000

Countdown’s on: November Flow Bootcamp. 

Secure your seat + certification voucher bonus now for the Complete Flow Course. 

https://flow-canvas.com/live-complete-flow-course/

 

 

#Flow  #Flownatics  #Salesforce Admin  #Salesforce Developer

4 comments
0/9000

💬 #Flownatics, mark it down. Next week we’re back with True to the Core Deep Dive: Flow Testing and Debugging. 💬 , mark it down. Next week we’re back with True to the Core Deep Dive: Flow Testing and Debugging.

Flow PMs @Sam Reynard, Adam White, and @Henry Liu will walk through recently delivered ideas, highlight new capabilities, preview what’s next, and answer your questions live. 

 

Trust us, you don't want to miss this. 

 

➡️ RSVP to get a reminder here. ⬅️ 

 

#True To The Core #IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects

0/9000