Today5 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 13The independent daily for Salesforce admins, developers and architects5 stories

Must-readFlow and admin

Winter '26 adds multi-column sorting and Flow version comparison (opens in a new tab)

Readers will learn which Winter '26 updates improve daily admin workflows, including multi-column List View sorting, enhanced Flow debugging, and localized report labels.

Winter '26 release

  • List Views
  • Flow Builder
  • Reporting and dashboards
Main update categories in the Winter '26 Salesforce release

The Winter ’26 release introduces several quality of life improvements for administrators, starting with List Views. Users can now sort records by up to five columns simultaneously, each set to ascending or descending order. Configuring this stays persistent until manually reset. Field pickers within List View controls also support type ahead search, allowing admins to quickly locate fields by typing characters and using keyboard shortcuts.

Flow Builder receives substantial updates to streamline automation design and management. Decision elements can now leverage Generative AI to analyze unstructured data and route records based on tone or urgency. Flows can automatically trigger when files attach to records, and newly created records can be referenced immediately without additional query elements. Debugging becomes easier with a resizable side panel and card based results that jump directly to canvas elements. Administrators can also compare flow versions side by side to track changes across autolaunched, scheduled, and record triggered types.

Reporting and dashboard capabilities expand with localization and security features. Labels for reports and dashboards can now be translated through the Translation Workbench, covering widget titles and footers. Exported reports include a beta option to block spreadsheet formula interpretation, preventing accidental execution of malicious strings. Dashboard charts in Lightning Experience will soon support reference lines, mirroring functionality previously limited to report charts. The author recommends testing these updates in a sandbox before production deployment.

Read the original at dev.to (opens in a new tab)

Worth reading?

RecommendedCareer and certifications

Salesforce and Pearson offer a free retake for failed certification exams this fall (opens in a new tab)

You will learn the exact dates, eligibility rules, and redemption steps for the current Pearson VUE free retake promotion.

Why read this

The article breaks down the actual financial savings and scheduling constraints so you can decide whether to plan your exam around this offer.

Salesforce and Pearson VUE are running a global promotion that waives the fee for one failed certification exam retake. To qualify, candidates must schedule, pay for, and complete their first attempt between September 29 and November 17, 2026. The promotion excludes Accredited Professional and CTA exams.

Claiming the voucher requires opting in through Pearson VUE to receive a unique code. Candidates must apply this code directly on Trailhead Academy during checkout, not on the general participating programs page. The retake must occur within a strict window from January 4 to April 7, 2027, and must match the original exam format, language, and delivery mode.

The financial benefit covers only the second attempt fee, effectively saving half the standard retake cost rather than the full price. Because the scheduled window includes holiday periods and forces a minimum seven-week gap after a late November failure, the author advises using the offer strategically only when already prepared to sit for a difficult exam without urgent hiring deadlines.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

RecommendedFlow and admin

How to invoke a Salesforce Screen Flow directly from a Slack workspace (opens in a new tab)

Readers will learn the exact steps to configure the Sales Cloud for Slack integration and route a Screen Flow into a Slack channel or direct message without leaving their messaging app.

The article outlines a method for running a Salesforce Screen Flow inside Slack by leveraging the Sales Cloud for Slack application. It begins with the prerequisite one-time connection between the Salesforce org and a Slack workspace, followed by assigning a Permission Set that includes system permissions for managing Slack app organization connections and user mappings.

Administrators must enable the Sales Cloud for Slack feature in Setup and install the corresponding app in their Slack directory. Once connected, creators can design a standard Screen Flow in Flow Builder and activate a hidden advanced setting labeled Make available in Slack during the save process.

To actually trigger the flow, a second autolaunched or Record-Triggered Flow acts as an invoker. This parent flow uses an action element to call the enabled Screen Flow, passing a Slack conversation identifier to determine whether the interactive button appears in a public channel or a private direct message. The piece concludes by noting that Salesforce automatically generates a background action for each enabled flow and advises clear button labeling for end users.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Architecture

Salesforce updates architecture diagram templates to reflect Agentforce and Data 360 (opens in a new tab)

You will learn how to select the correct diagram type for your audience and apply Salesforce updated template libraries to accurately represent current platform capabilities.

Salesforce architects spend much of their time communicating design decisions, and a clear architecture diagram gives teams a shared reference point that replaces long meeting notes and chat threads. Salesforce refreshed its Reference Diagrams, Architecture Gallery templates and Lucidchart shape libraries in June so they reflect Agentforce and Data 360, the renamed Data Cloud. The Cards library now includes preformatted Agentforce components, product names are updated, and new templates cover multi-cloud work coordinated by Agentforce, event-driven agent triggers and data flows with AI decisioning. Font sizes and border contrast were also improved for large-screen reviews, and some interaction process flow diagrams tied to Decision Guides and Fundamentals content were retired. The refresh did not change Salesforce’s five core diagram types, its Lucidchart partnership or its overall approach.

The five core types each answer a different question, so the choice should start with the audience. Capability maps show what business capabilities a solution must provide, without technical detail, and suit executives. Roadmaps add a time dimension for phased delivery and can show technical dependencies in business terms. System landscapes show the systems, products and connections in an estate, which helps with discovery and impact analysis. Solution architectures show how systems communicate and integrate, including authentication and data movement, and are the diagrams implementation teams use most. Interaction process flows show the numbered sequence of steps, agent actions and handoffs over time.

Most substantial projects use several of these diagrams, and they should tell a consistent story across each other. Architects are advised to start from a template in the Reference Architecture Gallery rather than a blank canvas, then adapt it to their scenario. For Agentforce designs, the article recommends splitting concerns across multiple diagrams rather than overloading one, and making human-in-the-loop points and data grounding visible to security, governance and business readers. Diagrams are not a substitute for entity relationship diagrams when data modeling is significant. The article closes by stressing that a good diagram makes the right information easy to understand for its particular audience, not that it contains the most detail.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Apex and platform

Seven Apex best practices for handling governor limits and bulk processing (opens in a new tab)

Readers will learn how to structure Apex transactions to avoid governor limit exceptions by applying bulkification patterns, optimizing data operations, and designing realistic test suites.

The article explains that Salesforce multitenancy requires strict resource management through governor limits that cap SOQL queries, DML statements, CPU time, and heap size. Developers are advised to treat these boundaries as foundational design constraints rather than post-development hurdles.

Core recommendations focus on eliminating database operations from iterative loops. The piece demonstrates collecting target identifiers into sets, executing single bulk queries, and populating maps for rapid lookups. It also shows how to accumulate records into lists for batch insertions while checking for empty collections beforehand.

Efficient use of Apex collections and comprehensive testing strategies receive equal emphasis. Writers are instructed to select appropriate collection types based on lookup needs and to validate logic against high record volumes. Testing must account for downstream automation overhead and varying data relationships to prevent unexpected limit exhaustion.

Finally, the guide outlines ongoing maintenance practices, including reviewing debug logs and refactoring inefficient code as data scales. It notes that persistent limit failures often stem from interconnected automation layers, requiring architects to evaluate broader system design alongside individual class performance.

Read the original at dev.to (opens in a new tab)

Worth reading?