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