This is the web version of the newsletter which you can subscribe »
Hello
Before we dive into this week's links, I've got something exclusive for you.
I reached out to the organizers and we’re doing a small giveaway exclusively for subscribers of this newsletter: 5 free tickets (the current ticket price is 999 PLN + VAT).
How it works:
- Fill in this quick form and answer one question (takes 1-2 minutes): https://tally.so/r/ZjV8No
- Deadline: Thursday, March 12, 23:59 CET
- Winners: Friday, March 13 (announced on LinkedIn + contacted by email)
- This is subscriber-only (existing and new subscribers have an equal chance - confirmed email addresses only)
- Important: if you win, you’ll need to be able to attend in person in Wrocław on March 20 (otherwise the ticket will go to someone else)
I'll be there too, so if you're coming, let's grab a coffee.
Now, onto this week's newsletter - there's plenty to unpack. Agentforce Builder got a major upgrade with better control and visibility, and Spring '26 keeps delivering practical updates like Flow Embedded Analytics and native Kanban boards. Plus, there's a solid discussion brewing about whether AI will really replace SaaS or if we're just watching another hype cycle play out.
Check the links below and see what catches your attention.
Grzegorz
For everyone
-
5 Salesforce Features Every Admin Needs in 2026
https://www.salesforceben.com/salesforce-features-every-admin-needs/
Salesforce keeps rolling out new features and updates that admins need to stay on top of - it's key to keeping things running smooth and helping users work better. In 2026, the big push is doing more with what's already there, focusing on optimization, reuse, and scaling up without always starting from scratch. Check out the five must-know features admins should watch in 2026 to level up their game and stay ahead. -
Why You Should Not Be Vibe Coding Salesforce Flows
https://www.salesforceben.com/why-you-should-not-be-vibe-coding-salesforce-flows/
Even though Salesforce Flow enthusiasts love Agentforce Vibes, using AI coding tools like this to build Flows isn't actually a good idea - just because you can do something doesn't mean you should, and there are solid reasons why vibe coding and Flow don't mix well together. -
Design Screen Flows With Intent Using Styling Overrides
https://admin.salesforce.com/blog/2026/spring-26-design-screen-flows-with-intent-using-styling-overrides
Spring '26 adds styling overrides to Flow Builder, letting admins customize how screen flows look without needing code - but with great power comes the need for a smart plan to avoid messy, inconsistent designs that clash with brand guidelines, so it's worth thinking through a solid approach before diving in. -
Is this the Death of the Standard Admin: Why Salesforce Data 360 is Your New Reality
https://www.desynit.com/blog/why-salesforce-data-360-is-your-new-reality/
Jenny Bamber, Head of Salesforce Success at Desynit, thinks the traditional Salesforce Admin role is about to change big time - similar to how the Developer role shifted years back. After over a decade working as an Admin, watching the job evolve from basic password resets to complex Flow work, the next major shift is coming: moving from Standard Admin to Data 360/AI Admin. Data 360 is the game-changer pushing this transformation forward. -
How to use the Kanban Board Component in Flow
https://salesforcegeek.in/how-to-use-the-kanban-board-component-in-flow/
Spring '26 introduced a native Kanban Board component for Screen Flows that brings visual workflow management straight into automation without needing custom coding - basically you can display records as cards grouped into columns by status or stage, show summary totals for each column, and display up to five fields per card, making guided processes way more engaging for people reviewing and approving work. -
Einstein Conversation Insights Gets Smarter in Spring '26
https://salesforcebreak.com/2026/02/26/einstein-conversation-insights-spring-26/
Einstein Conversation Insights is getting a major upgrade in Spring '26 that makes call recordings way more useful - instead of just sitting there as summaries, they now turn into real intelligence that can automatically trigger actions, coaching tips, and reports across the sales process. Salesforce is basically connecting call data, AI, and CRM together so conversations become actionable insights that flow through the whole organization. If someone manages Salesforce setup, builds reports, or handles sales training, this update is going to change how conversation data moves through their system. -
Improved Accessibility Features in Salesforce Omnistudio
https://developer.salesforce.com/blogs/2026/02/improved-accessibility-features-in-salesforce-omnistudio
Salesforce Omnistudio just upgraded over 45 elements to meet top accessibility standards (WCAG 2.1 and 2.2), making Omniscripts and Flexcards way more user-friendly for everyone - especially people using screen readers and other assistive tech. The update fixes common problems like buttons disappearing for screen readers or colors blending together, which usually costs time, trust, and potential legal issues. Now building accessible apps without headaches is actually possible. -
Introducing Bolt Logger - A Unified Error Logging Framework for Salesforce
https://www.salesforcebolt.com/2026/02/Bolt-Logger-Salesforce-Error-Logging-Framework.html
Salesforce debugging is messy - standard logs waste time, Flows crash silently, and LWC errors never reach the server. Plus, critical errors can spam thousands of emails and drain your limits fast. Bolt Logger fixes all this by creating one unified "Black Box" for the entire Salesforce org. It captures errors from Apex, Flow, LWC, and Batch jobs in a single central location - no noise, no clutter, just clean error tracking. Built on Platform Events, Bolt Logger keeps logs safe even when transactions fail, and it works completely independent of email limits, so nothing gets lost or missed. -
Why Salesforce's Q4 Results Will Prove If the 'SaaSpocalypse' Is Real
https://www.salesforceben.com/why-salesforces-q4-results-will-prove-if-the-saaspocalypse-is-real/
Salesforce's Q4 results drop next week, and it's make-or-break time. The company saw stock gains after Q3 showed solid revenue and wins with Agentforce and Data 360, but CRM stock has tanked 23% since December as the "SaaSpocalypse" panic spreads - basically, investors worry AI can do what old software does, but faster and cheaper. This earnings report will show whether those fears are justified or if Salesforce can prove it's still got what it takes. -
Salesforce Removes Paywall and Makes Flow Orchestration Free
https://www.salesforceben.com/salesforce-removes-paywall-and-makes-flow-orchestration-free/
Salesforce just dropped the paywall on Flow Orchestration - it's now free and built right into standard Flow, so no extra costs or licensing headaches. If folks were hesitating before because of the price tag, that's no longer a reason to wait. -
Flow Embedded Analytics and Flow Logging
https://salesforcetime.com/2026/02/28/flow-embedded-analytics-and-flow-logging/
Salesforce Spring '26 release brings Flow Embedded Analytics to all orgs, making Flow debugging way easier - now it shows real execution data right in Flow Builder so builders can see total runs on each element, check element status, and track total duration without guessing what's actually happening at runtime. -
Salesforce Fact #982 | Field integrity exception while deploying a flow
https://sfactsabhishek.blogspot.com/2026/02/salesforce-fact-982-field-integrity.html
When deploying a flow that calls a subflow and uses its outputs, a field integrity exception error might pop up saying "unknown (the element has an invalid reference to" - basically meaning the flow can't find what it's looking for because something's linked wrong or missing, so double-check that all the subflow connections are set up correctly and the output references actually exist before trying to deploy again.
For devs
-
Error Logging Framework in Salesforce for LWC
https://salesforcegeek.in/error-logging-framework-in-salesforce-for-lwc/
Building fast Lightning Web Components for Salesforce is great, but it brings a challenge - catching errors before users spot them. An Error Logging Framework solves this by automatically capturing and tracking both client and server errors, storing them for analysis, and keeping everything running smoothly. This approach beats waiting around for angry user reports and becomes essential for big Salesforce setups, production environments with strict rules, and teams doing continuous delivery. The blog walks through building and setting up a complete error logging system for LWC from start to finish. -
How to Use Apex for Effective PDF Document Generation
https://salesforcecodex.com/salesforce/how-to-use-apex-for-effective-pdf-document-generation/
Apex PDF generation is getting a major upgrade in Summer '26. Salesforce is fixing the annoying problem where PDFs look totally different from Visualforce pages by making Blob.toPdf() use the same rendering service. This means better consistency and way fewer formatting headaches when creating PDF documents - no more surprises when the output doesn't match what was expected on the screen.
For architects
-
A Salesforce Architect's Guide to Data Model Relationships
https://www.salesforceben.com/a-salesforce-architects-guide-to-data-model-relationships/
Salesforce Architects need to understand data relationships both inside and outside Salesforce. While traditional Entity Relationship Diagrams use standard notation, Salesforce specifically uses Lookup and Master-Detail relationships - each works differently on the platform. This guide breaks down key concepts like cardinality and ordinality, plus standard notation styles like Information Engineering notation that architects use to map data connections. Learning these basics gives technical teams the vocabulary to read and understand data models across any platform. -
How to Choose a Salesforce Integration Method: Native Tools vs. Connectors vs. iPaaS
https://www.salesforceben.com/how-to-choose-a-salesforce-integration-method-native-tools-vs-connectors-vs-ipaas/
Picking the right way to connect Salesforce with NetSuite can be tricky - there's no simple playbook, so someone learned this the hard way after testing different approaches. Here's why it matters: companies that link their CRM and ERP systems see real results - customer satisfaction jumps by over 20% and operations run smoother. This breakdown covers three main methods to make this connection work: native tools built into the systems, connectors like Zapier, and iPaaS platforms like Workato or Breadwinner - each one has its own pros and cons based on what actually works in the field.
Reddit Discussions
-
I saw first hand why $CRM stock is down so much and why enterprise AI is in for a surprise
https://old.reddit.com/r/salesforce/comments/1r5g5u6/i_saw_first_hand_why_crm_stock_is_down_so_much/
Someone spotted a major problem with Salesforce and enterprise AI hype - companies are already doing with Microsoft Copilot what vendors are promising with expensive, complex AI integrations that take months to build. At an insurance conference, agency owners showed how they're using Office 365 Copilot for everyday tasks like summarizing emails and drafting client responses, plus some genuinely useful workflows. Nothing fancy or complicated - just real problems getting real solutions, fast. This explains why enterprise AI vendors are getting pressure and why their stock is tanking - people don't need months of development and massive budgets when simple AI tools already solve their problems right now. -
Why is it so f*** hard to log notes in SF?
https://old.reddit.com/r/salesforce/comments/1qxid3y/why_is_it_so_f_hard_to_log_notes_in_sf/
Frustration comes with Salesforce's notes feature compared to modern tools like Notion and voice transcription apps. The main issue - Salesforce notes can't be reported on, so finding all notes mentioning a specific problem is basically impossible. Plus, notes buried in tasks or calls aren't visible on the record screen without clicking through everything. Workarounds exist - like creating custom fields or objects - but they don't work properly either. Custom fields can't sync across related objects (like showing an opportunity note on the account), and custom objects can't link to multiple contacts at once like activities can. Bottom line: it's ridiculous that logging a simple note in a CRM requires all these hacks. The person's asking Salesforce to finally build a notes feature that actually works - something searchable and reportable would be game-changing, especially now that Salesforce integrates with Notion, Zoom, and transcription tools anyway. -
I saved a record... why did 5 other things just change? — I built a tool that answers this
https://old.reddit.com/r/salesforce/comments/1r69i5v/i_saved_a_record_why_did_5_other_things_just/
Check out SF-Intel Studio, a Chrome extension that works like a detective for Salesforce - it shows exactly what happens behind the scenes when you do stuff like clicking buttons, running flows, or saving records. The Live Trace feature captures all the automations that trigger and tracks which records get created, updated, or deleted as a result. Best part? No packages, no Apex code, no org installation needed - just install the extension and you're good to go. -
Client wants Agentforce but their flows still fail every Tuesday
https://old.reddit.com/r/salesforce/comments/1p09jwi/client_wants_agentforce_but_their_flows_still/
User is getting asked to implement Agentforce in an org that's basically a mess - their lead assignment flow breaks every Tuesday, they've got 47 different spellings of the same company names in accounts, opportunities stuck since 2022, and reports that take forever to load because nobody ever archived anything. They're wondering if it's worth pushing back on the AI agent project to actually fix the foundation first, or if that just makes them look outdated. The whole thing feels like installing a smart home system when the light switches don't even work. They're curious how others handle this situation - just build it anyway and deal with the chaos, or tell clients they need to clean house first?
For AI enthusiasts
-
Copilot Instructions - AI Ruleset for Apex & LWC
https://salesforcediaries.com/2026/02/26/copilot-instructions-ruleset-apex-lwc/
This is basically a ready-to-use guide for setting up AI rules when coding in Apex and LWC - think of it like giving AI tools like Github Copilot or Claude Code specific instructions on how to write Salesforce code. The whole point is to make sure that whenever the AI generates code for classes, triggers, or LWC components, everything automatically meets production quality standards right from the start - no need to fix things afterward. -
If AI Will 'Replace 50% of SaaS', Why Is Anthropic Hiring a Salesforce Admin?
https://www.salesforceben.com/if-ai-will-replace-50-of-saas-why-is-anthropic-hiring-a-salesforce-admin/
Mistral AI's CEO claims AI will replace over 50% of current business software, sparking fresh debate about SaaS dying out. The company, valued at $13.8B, says enterprises are shifting away from traditional software toward AI solutions - a "replatforming" happening right now. However, the CEO notes that core data management systems won't disappear since they work alongside AI. While this sounds dramatic, it's worth noting the CEO has clear reasons to hype AI's potential - basically, people pushing the AI revolution narrative are telling us AI will revolutionize everything. The real story's probably somewhere in the middle, not as extreme as the headlines suggest. -
Build With Confidence: Inside the New Agentforce Builder
https://admin.salesforce.com/blog/2026/build-with-confidence-inside-the-new-agentforce-builder
Salesforce just dropped the new Agentforce Builder - a fresh way to build AI agents with way more control and clarity. The upgraded Atlas Reasoning Engine now uses a graph-based system that lets you actually see and customize how the agent flows work, separate from the conversational parts. This means you get more predictable results instead of guessing what might happen. Before, the old version just took prompts and figured out what to do next, but now admins can map everything out, test it, and tweak the behavior exactly how they want it. Same core Agentforce concept, but building and controlling agents just got a whole lot easier.
View upcoming Salesforce events (next 7 days)
 |
Grzegorz Skaruz
|
If you no longer want to receive messages from me, you can always unsubscribe