Today4 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 16The independent daily for Salesforce admins, developers and architects4 stories · 1 brief

Must-readApex and platform

Custom sharing reasons now roll out for standard objects alongside a setting to preserve manual shares (opens in a new tab)

You will learn how to use the new custom sharing reason feature on standard objects and configure the org-wide setting that keeps manual shares intact during record transfers.

Why read this

The article provides exact metadata and Apex examples so you can implement these changes immediately.

Keep Manual Shares

  • Available immediately in Sharing Settings
  • Keeps user manual shares after ownership changes
  • Best for teams relying on manual distribution

Custom Row Causes

  • Rolls out via Metadata API through October
  • Defines programmatic sharing reasons in code
  • Best for developers using Apex or Flow
Two new Salesforce sharing features help records keep access after owner changes

Salesforce is introducing two enhancements to the sharing model that eliminate long-standing workarounds for standard object access control. The first is an org-wide toggle called Keep Manual Shares when Transferring Records, which is available immediately in Sharing Settings. Enabling it ensures that manual shares survive ownership changes without requiring custom code or triggers.

The second enhancement rolls out through October and allows developers to define custom row causes on standard objects using the Metadata API. Previously, Apex managed sharing was restricted to Custom Objects. The update lets you declare a sharing reason like On Call Expert directly in the CustomObject metadata, then reference it in Apex share records or Flow actions. This separation keeps programmatic shares distinct from user manual shares and prevents automatic deletion when owners change.

The guidance recommends evaluating existing code that creates CaseShare, AccountShare, or similar records. Teams building shares via Apex or Flow should migrate to custom row causes to maintain auditability and stability. Those relying purely on manual distribution can simply enable the preservation setting. Both features arrive ahead of November updates that will bring management capabilities to Agentforce and Setup.

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

Worth reading?

RecommendedAgentforce and AI

Salesforce unveils an interface layer to connect platform data and permissions to AI tools (opens in a new tab)

Readers will understand how the new interface layer exposes Salesforce data, workflows, and existing permissions to external and internal AI applications without replacing the core CRM.

Why read this

The piece also clarifies the security model, the role of the Headless Toolkit, and how this capability differs from Agentforce.

Salesforce AIforce is a live interface layer that brings Salesforce data, workflows, business logic, permissions and governance into AI tools such as Claude, Slack and Lightning, so people can query records, update them and trigger workflows without opening the Salesforce app. Announced at Dreamforce, it is positioned as the top layer of Salesforce’s Agentic Enterprise architecture, above Agentforce, Customer 360 and Data 360. The Headless Toolkit, which exposes the platform through MCP servers, APIs, plug-ins and skills, connects these layers. Its three launch surfaces are Claudeforce (Salesforce in Claude, with 37 prebuilt sales skills, now in beta for all customers), Slackforce (Slackbot, Slack CRM and related tools) and Agentforce Coworker in Lightning.

The article explains that AIforce differs from Agentforce: Agentforce builds and runs the agents that do the work, while AIforce is the interface through which people and agents reach Salesforce from outside the app. Coworker bridges the two by calling agents a company has already deployed. On security, the article describes four points: requests run under the user’s existing permissions, hosted MCP servers are inactive until an admin enables them and are logged through Event Monitoring, approval can be required for changes or deletions, and Salesforce says business data is not retained by the model provider under Zero Data Retention. The author advises confirming those terms in the contract, and notes that pricing and availability can change and vary by region.

The piece also covers the naming question: Marc Benioff said on October 9 that AIforce is now SIforce, but Salesforce’s own product pages still used AIforce at the time of writing. It treats the name change as a signal to plan around permissions, data models and integrations rather than brand labels. A case study on BACA Systems, a 50-person manufacturer, describes an Inventory Agent in Slack, a Slack channel per field project, and an ACH payments module that removes card fees, with a projected saving of about $200,000 a year. The article stresses that these are Salesforce-published projections and that BACA’s ERP runs natively on Salesforce, which is unusual.

Finally, the article offers an illustrative scenario for firms whose ERP is SAP, Oracle or NetSuite, where a MuleSoft-style governed API layer is needed to answer cross-system questions. It closes with a six-step readiness checklist (data foundation, permissions, external systems, MCP policy, a single-team pilot, and monitoring) and the author’s view that AIforce amplifies whatever data and permission quality already exists, so organizations should start with packaged surfaces and proof for trust claims before building custom experiences.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?

Apex and platform

A VS Code extension runs anonymous Apex and SOQL with a single keyboard shortcut (opens in a new tab)

Readers will learn how to install and configure Virga to execute throwaway Apex and SOQL scripts without leaving the editor.

Why read this

The piece also explains how the extension resolves common language server completion issues and disables telemetry during local runs.

Virga is a free VS Code extension designed to streamline the execution of throwaway Apex and SOQL scripts directly within the editor. Setup requires VS Code version 1.90 or newer, the Salesforce CLI on the system path, and an active Salesforce DX project. Users create dedicated scratch tabs for either language, trigger execution with a keyboard shortcut, and receive formatted output showing compilation status, debug logs, governor limits, or flattened query results.

The tool handles execution through a temporary file copy rather than direct command line arguments, which prevents partial edits from affecting the run. It achieves a seamless experience by applying a brief auto-save delay that clears tab dirtiness markers, allowing instant closure without save prompts. Scratch files persist in a version control ignored folder and survive editor restarts, while conflicting keymaps are handled to preserve the shortcut exclusively for scratch contexts.

Beyond basic execution, the extension patches gaps in the standard Salesforce Extension Pack. It adds completion support for inner types declared in the same file, identifies and offers quick fixes for parameter shapes that crash the language server, and supplies missing snippets for annotations and user mode operations. Privacy is maintained by automatically disabling Salesforce CLI telemetry for each run, though administrators can enforce global telemetry suppression through standard configuration commands.

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

Worth reading?

Apex and platform

How elastic limits extend Async Apex capacity and throttle processing in Winter '27 (opens in a new tab)

You will learn how the Winter '27 extension of elastic limits increases Async Apex capacity while throttling throughput, and how to monitor usage with the OrgLimits class.

The Winter ’27 release extends the beta capability of elastic limits to Batch jobs, following its initial introduction for Queueable and Future methods in Summer ’26. When standard asynchronous governor limits are reached, the system allows additional enqueues up to a secondary cap calculated as the minimum of two million or the standard limit. Enqueued jobs beyond the baseline trigger throttling, which slows active processing and restricts Batch jobs to a single concurrent instance.

Developers can track consumption using the OrgLimits class, specifically querying the DailyAsyncApexElasticExecutions metric alongside the standard daily limit. The feature remains exclusive to production environments, meaning sandbox and trial orgs do not receive the extra capacity. Salesforce intentionally omits exact throttling metrics to prevent teams from treating the slowdown behavior as a guaranteed service level.

Scheduled Apex does not support elastic limits because the feature trades execution speed for additional volume, which conflicts with the time-sensitive nature of scheduled runs. The author advises using the extra capacity strictly as a resilience buffer rather than a primary scaling strategy, recommending that organizations investigate root causes when they regularly approach baseline limits.

Read the original at Bob Buzzard Blog (opens in a new tab)

Worth reading?

In brief