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.
Issue · #198 19 articles · sent Tue Nov 3 · here since Thu Nov 5
5 IdeaExchange Features Delivered, Trailblazer Knowledge vs Slack Move, AI Agent Billing Talks With Partners
From the curator, Grzegorz Skaruz: This week felt like one of those moments where Salesforce quietly rewrites a few rules and expects us to just roll with it. The biggest one: after 20 years, the Trailblazer Community forums are heading to Slack. I've got thoughts on what we might lose in that move, and what to prep before November.I'm also digging into the ongoing MFA rollout mess - the timelines keep shifting, and support messages aren't exactly clearing things up. If you're still unsure where you stand, you're not alone. Read the whole note
This week felt like one of those moments where Salesforce quietly rewrites a few rules and expects us to just roll with it. The biggest one: after 20 years, the Trailblazer Community forums are heading to Slack. I've got thoughts on what we might lose in that move, and what to prep before November.I'm also digging into the ongoing MFA rollout mess - the timelines keep shifting, and support messages aren't exactly clearing things up. If you're still unsure where you stand, you're not alone. On the business side, Salesforce opened talks with partners over confusing AI agent billing charges, and the latest ecosystem report tackles the question a lot of us are quietly asking: is a Salesforce job still worth chasing in 2027? Grab a coffee and dig in - there's more below worth your time.
Subscribers read this issue two days before it landed here.
Get it in your inboxArticles
2 articles match · Clear filters
-
Salesforce Insights in 5 MinutesIssue #198For architects
Context Is an Architecture Decision
Ever seen a Salesforce org where everything technically works, but nothing explains itself? Random field names, blank descriptions, Flows called "Decision_4" - and only one person on the team actually knows why. For years, teams got by on tribal knowledge. But now AI is being plugged into these systems and expected to understand the business - and suddenly missing context becomes a real problem. Metadata isn't just the technical setup (fields, Flows, objects); it's also the explanation of why things exist and how they connect. That explanatory layer used to be "nice to have" documentation. With Agentforce, it becomes context an AI actually needs to reason properly. Time to rethink documentation.
-
Salesforce Insights in 5 MinutesIssue #198For architects
Salesforce Experience Cloud 50K User Limit: Architecture Lessons from a 200K E-Commerce Portal
Building an Experience Cloud portal for a few thousand users is easy - but scaling to 200,000 customers is a whole different game. During a real e-commerce deployment using Person Accounts and Customer Community Plus Login, a hidden 50,000 account-ownership limit blocked onboarding after the site was already live in production. Salesforce Support couldn't raise the cap, forcing a rethink of the entire architecture. This raises a big question: how do you scale Experience Cloud past that role and ownership bottleneck? This piece digs into the limits, possible fixes, and the key architectural calls you need to make before launching a large customer portal.
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