Salesforce news
The best of the Salesforce ecosystem, filtered for you every week by Grzegorz Skaruz, plus the articles the ORGanizer community suggests. Vote for what matters to you and say what you think of it.
This week’s issue · #197 18 articles · sent Tue Oct 27 · here since Thu Oct 29
Design a System of Record, Architecture Diagrams Guide, Agentforce Demand Lagging Despite Trials
From the curator, Grzegorz Skaruz: Another week, another mix of "this changes everything" and "wait, did we just agree to that?" moments in the Salesforce world.I'm digging into a practical one first: designing a proper system of record across multiple objects, because scattered data isn't a "which field goes where" problem, it's an architecture problem. Speaking of architecture, there's also a solid refresh on diagramming tools and templates worth bookmarking if you spend more time explaining your org than building it. Read the whole note
Another week, another mix of "this changes everything" and "wait, did we just agree to that?" moments in the Salesforce world.I'm digging into a practical one first: designing a proper system of record across multiple objects, because scattered data isn't a "which field goes where" problem, it's an architecture problem. Speaking of architecture, there's also a solid refresh on diagramming tools and templates worth bookmarking if you spend more time explaining your org than building it. Then there's Agentforce. Adoption numbers look great on paper, but the gap between "tried it" and "committed to it" is getting harder to ignore. I'm covering why the pilot phase is ending and what companies are actually running into now that the hype is settling. And if you're on Winter '27 prep, I've got the critical changes worth testing before they test you. Grab your coffee and dig in.
Subscribers read this issue two days before it landed here.
Get it in your inboxArticles
18 articles match · Clear filters
-
Salesforce Insights in 5 MinutesIssue #197For architects
How to Design a System of record Across Multiple Objects in Salesforce: Multiple Entry Points, One Source of Truth
Ever notice how the same info - like a customer's address or banking details - ends up scattered across different Salesforce objects? It happens because each team builds their own process (a Case, an OmniScript, a form) and just adds fields where it's convenient. Over time, you end up with multiple versions of the same data, and no one knows which one to trust. The real fix isn't asking "where do I put this field?" - it's asking "what business entity does this info belong to, and where should the one true version live?" As Salesforce orgs grow, getting this right matters more and more.
-
Salesforce Insights in 5 MinutesIssue #197For architects
Ultimate Guide to Salesforce Architecture Diagrams
Salesforce Architects spend most of their time communicating, not just building. Good architecture diagrams help everyone - stakeholders, delivery teams, everyone - get on the same page without endless meetings or Slack threads. Since Salesforce has evolved a lot (hello, Agentforce), the diagram tools needed an update too. In June, Salesforce refreshed its Reference Diagrams, Architecture Gallery templates, and Lucidchart shapes to match. This guide covers what's new and how to pick the right diagram type for your audience.
-
Salesforce Insights in 5 MinutesIssue #197For everyone
85% of Customers Have Tried Agentforce, But Demand Hasn't Picked Up. Why?
Agentforce's numbers look huge on paper - 29,000+ paid deals, $1B+ in AI revenue, and nonstop marketing push from Salesforce. But a closer look tells a different story. An Oppenheimer survey found almost 90% of customers have tried or deployed it, yet nearly half are still stuck in testing or pilot mode. Trying it out isn't the same as fully adopting it, and right now, most companies aren't ready to go all in. The big question: when will they actually commit?
-
Salesforce Insights in 5 MinutesIssue #197For AI enthusiasts
Agentforce Now Has to Prove It's Worth the Investment
Salesforce AI has moved past the "just try it" phase - pilots and experiments are over, and companies are now either scaling up Agentforce or quietly pausing it. The hype is fading, and the real challenges are surfacing: messy data, unclear ownership, cost, trust issues, and the big question - is it actually worth the money? This isn't because the tech failed, but because just showing people are using it isn't enough anymore. Salesforce AI now needs to prove real value, not just adoption.
-
Salesforce Insights in 5 MinutesIssue #197For architects
Salesforce OAuth Username-Password Flow Retirement
Salesforce is killing off the OAuth 2.0 Username-Password Flow on February 20, 2027. If your integrations still rely on it, they could just quietly stop working - no warning, no error, just records that stop updating. That's the scary part. Best move: check your integrations now and switch to a supported auth method before the deadline hits, so nothing breaks without you noticing.
-
Salesforce Insights in 5 MinutesIssue #197For everyone
The SaaSpocalypse Didn't Kill Salesforce, But It Could Change It Forever
The so-called "SaaSpocalypse" hasn't killed off traditional software like everyone predicted - software stocks bounced back and big vendors like Salesforce are still posting solid numbers. Turns out AI isn't just making existing software pointless. But that doesn't mean nothing's changing. If AI agents start handling tasks across different systems without anyone needing to log into a dashboard, the whole SaaS setup could still get shaken up. The real question now: what happens to Salesforce and companies like it as AI reshapes how software actually gets used?
-
Get it in your inbox
Get the full issue first
Every week, Grzegorz Skaruz reads through the Salesforce ecosystem so you don't have to. This section features a selection from his newsletter. Want the full list of 20+ articles, delivered every Tuesday before it lands here? Subscribe for free.
Free, no spam – unsubscribe anytime.
-
Salesforce Insights in 5 MinutesIssue #197For AI enthusiasts
Salesforce Renames AIforce to 'SIforce' After Trump Order
Salesforce just renamed its AIforce feature to SIforce, says CEO Marc Benioff - jumping on the "super intelligence" trend taking over AI talk. This isn't the first switch either: the tool started as Headless 360 at TrailblazerDX, became AIforce at Dreamforce last month, and now it's SIforce. That's three names in about six months for the same agentic integration layer.
-
Salesforce Insights in 5 MinutesIssue #197For AI enthusiasts
Business or Technical Skills: Which Should You Improve in the AI Era?
Senior Salesforce pros are at a crossroads in the AI era. New AI tools create fresh chances to sharpen technical skills, but "vibe-coding" tools now let non-coders build solutions that can almost rival professional work. Meanwhile, business skills haven't lost their value. So the big question is: with AI shaking things up, should you focus on growing your business skills or your technical ones?
-
Salesforce Insights in 5 MinutesIssue #197For AI enthusiasts
Salesforce's New AI Agent Piper Might Be a Little Too Human
Salesforce just rolled out Piper, a new AI sales agent, plus a bunch of other AI agents, showing them off at Dreamforce 2026 and across their site. Sure, these tools pack real functionality - but something about how they're designed feels a bit off, almost too human. And it's not just one person's gut reaction - other Salesforce folks have mentioned feeling the same weird vibe.
-
Salesforce Insights in 5 MinutesIssue #197For AI enthusiasts
How to Use AI to Prevent Scope Creep in Salesforce
Scope creep sneaks into Salesforce projects fast - one extra field here, a tweaked requirement there, and suddenly the build's way bigger than planned. AI won't stop people from changing their minds, but it can help spot vague requirements, flag risky changes early, and keep a clear record of what was actually agreed. Used right, it catches small issues before they snowball into big delivery headaches.
-
Salesforce Insights in 5 MinutesIssue #197For AI enthusiasts
Building Agentic RAG: Setting Up Web Crawlers in Data Cloud (Part 1)
AI agents are only as good as the data behind them. In fast-changing fields like aviation, things like routes and schedules change all the time - if an agent uses old info, it can give wrong answers and lose customer trust. This guide shows how to build a full Agentic RAG pipeline in Salesforce using Data Cloud, Agentforce Studio, and Prompt Builder: setting up a web crawler to pull in fresh data, turning it into searchable chunks, creating a custom retriever, and deploying an Agentforce subagent that gives accurate, real-time answers.
-
Salesforce Insights in 5 MinutesIssue #197Winter'27
Salesforce Winter '27 Release: 15 Critical Changes to Test
If your org upgraded in October and nothing's broken yet, great - but some risky changes only show up later or hit specific integrations. Most issues since the upgrade aren't bugs, just overlooked changes. Winter '27 brings 15 updates: 5 that could break stuff, 5 Flow/admin wins, and 5 Agentforce updates. If you're still doing a lot of automation manually, it's worth checking which Sales Cloud workflows to automate first. Also note: Flow Tags, which would've let admins label and group flows, got pulled from this release back in mid-September 2026.
-
Salesforce Insights in 5 MinutesIssue #197Winter'27
Collection Filter Criteria Resource in Flow
Salesforce's Winter '27 release brings a new Flow resource called Collection Filter Criteria. It might look similar to Collection Filter and Collection Sort since it also filters and sorts records, but it actually works differently and opens up some neat possibilities. It won't fit every situation, but in the right cases it can simplify Flows and cut down on the number of elements needed. This post breaks down how it works, how it's different from the other two, and when it's worth using.
-
Salesforce Insights in 5 MinutesIssue #197Winter'27
Elastic Limits for Async Apex Jobs in Winter '27
Elastic limits for async Apex jobs (Queueable, Future, and now Batch) stay in beta for Winter '27. Basically, it's a safety net that kicks in when your async jobs suddenly spike past normal governor limits, keeping things running smoothly instead of crashing.
-
Salesforce Insights in 5 MinutesIssue #197For everyone
Collection Filter Criteria Resource in Salesforce Flow
Salesforce's upcoming Collection Filter Criteria Resource is a game-changer for Flow Builder. Unlike typical small admin tweaks, this one could seriously transform how automations are built. It's part of the Winter '27 preview, and it's set to make handling collections way easier and smarter than before.
-
Salesforce Insights in 5 MinutesIssue #197Reddit Discussions
Where does your team draw the Flow vs Apex line in 2026?
Asking where other teams draw the Flow vs Apex line these days. For a mid-sized org, simple record-triggered stuff stays in Flow, but once it has multiple loops, cross-object branches, or needs solid bulk handling, it gets harder to test than just writing a small Apex service. The tricky zone is medium-volume integrations (5-20k records) - Flow can technically do it, but error handling and retries get messy. Wants to know what's actually working for people in production in 2026 - do you keep most logic in Flow and only pull out the heavy stuff to Apex, or set your complexity bar lower than that?
-
Salesforce Insights in 5 MinutesIssue #197Reddit Discussions
Is Salesforce giving Claude a little too much power?
Someone's wondering if Salesforce is handing Claude a bit too much control these days - pulling data, updating records, triggering actions, basically doing everything inside the CRM. The real question: if Claude can handle all that from its own chat, why even open Salesforce anymore? Sure, Salesforce still owns the data and permissions underneath, but it feels like Claude's becoming the actual interface people use, with Salesforce just running quietly in the background. Not sure if this is just where enterprise software is heading, or something we'll look back on and think "wait, we gave an AI THAT much access?" Curious what other Salesforce folks think.
-
Salesforce Insights in 5 MinutesIssue #197Reddit Discussions
I'm afraid of performing mass updates
Mass updates on old records really freak this person out, so they tend to avoid them whenever possible. Last task was updating 81,000 records with a new payment date, but they ended up on sick leave before tackling it. Big worry is not knowing how to be sure nothing breaks, plus no clear way to roll back changes afterward. Checking every field and value across 81k records isn't realistic, and there's also fear of hidden blockers like triggers or validation rules messing things up. Basically asking for a solid, clear approach to handle mass updates safely without losing sleep over it.
News in this section is curated by Grzegorz Skaruz for his weekly newsletter, Salesforce Insights in 5 Minutes. Devs, admins and architects get the full issue every Tuesday - free, no spam, unsubscribe anytime. About the newsletter