Today4 stories · 2 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 38The independent daily for Salesforce admins, developers and architects4 stories · 2 briefs

Must-readDevOps

Agentforce agents move to AiAgentDefinition metadata types in API version 68.0 (opens in a new tab)

You will learn how the new AiAgentDefinition and AiAgentDefinitionVersion types replace Bot, GenAiPlannerBundle and AiAuthoringBundle for Agentforce agents, how to write a manifest and retrieve a single version with its dependencies, and which deployment rules and migration steps apply.

Agentforce agent at API 68.0

  • AiAgentDefinition
  • AiAgentDefinitionVersion
  • AiAuthoringBundle
The three old metadata types and the two new types that replace them

Winter ’27 introduces two metadata types for Agentforce agents at API version 68.0: AiAgentDefinition, which holds agent-level settings, and AiAgentDefinitionVersion, which holds one version’s settings, messages and an inline planner with its subagents and actions. Under the previous structure, one agent was spread across the Bot, GenAiPlannerBundle and AiAuthoringBundle types, with generated name suffixes, hard-to-find welcome messages and folder names that changed between retrieves. The author compares a sample agent retrieved at API 67.0 and 68.0, showing that the content was identical and only the names and packaging changed.

At API 68.0, Agentforce agents must use the new types, and retrieving or deploying them as Bot or BotVersion returns an error. The # delimiter lets a manifest or the –metadata flag select a single version, such as TestAgent#1, all versions with TestAgent#, or every version of every agent. Salesforce CLI version 2.149.9 or later is needed, and the –root-type-with-dependencies AiAgentDefinitionVersion flag pulls in the parent definition, the authoring bundle and the Flows, Apex classes and Prompt Templates the version uses. The dependency retrieve is limited to 25 requests per day, 100 components per request, and one level deep.

Deployments fail if the old and new formats are mixed, if a version is deployed without its definition existing in the target org or the same deployment, or if the Agent Script source is omitted. The author also notes that the agent user from the source org must be replaced for a draft agent, and recommends switching to API 68.0 in its own commit and updating any scripts that parse the old files.

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

Worth reading?

RecommendedArchitecture

Modelling FCA complaints data in Salesforce and avoiding the UTC time zone trap (opens in a new tab)

You will know how to model the fields COM001 needs for Cases, including a UK-local date that puts complaints in the correct half-year.

Why read this

You will also know how to test the setup before the 2027 deadline.

  1. Complaint received in UTC
  2. Convert to Europe/London date
  3. Store in Date_Received_UK__c
  4. Derive H1 or H2 formula
  5. Group report by legal entity
How the UK date feeds the half-year label used in COM001 reporting

From 1 January 2027, UK financial services firms will report complaints to the FCA in a new return, COM001, covering fixed half-years. The article sets out a data model for this built from standard Salesforce features, for orgs that hold complaints as Cases. Group reporting is removed, so each complaint needs a required legal entity, held as a restricted picklist or a lookup to a reference object that compliance controls. Every trading name and acquired brand must map to exactly one entity.

The return counts complaints from vulnerable customers and complaints about a failure to consider or respond to vulnerability, which can overlap. The author recommends two separate checkboxes rather than one picklist, with Field History Tracking switched on. Standard history is kept for 18 months, or 24 months via the API, unless Field Audit Trail is enabled, so it should not be relied on for longer retention.

The main pitfall is time zones. Datetime values are stored in UTC, so a complaint received just after midnight on 1 July during British Summer Time falls on 30 June in UTC and lands in the wrong half-year. The fix is a separate date field holding the UK date, set in a before-save trigger or invocable Apex using the Europe/London time zone, with the same done for the closed date. A formula on that date field then derives the half-year label, and reports are grouped by legal entity and that label.

The article also advises keeping the reason for a vulnerability marker in a separate field or related record, protected by field-level security, since health details can be special category data under UK GDPR. Before 1 January, it recommends testing a complaint created at 00:30 UK time on 1 July, running the same report twice a week apart, and confirming that changes to a vulnerability marker on a closed complaint are logged. The exact field names and validations are in the FCA’s COM001 Data Reference Guides.

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

Worth reading?

Releases

Salesforce Maps mobile app retires on 31 August 2026 (opens in a new tab)

You will learn that the standalone Salesforce Maps app and Maps Live Tracking Mobile are retired on 31 August 2026, where reps should go instead, and what a self-owned field app would involve.

  1. 31 Aug 2026: Standalone Salesforce Maps app retired
  2. 31 Aug 2026: Maps Live Tracking Mobile retired
Key dates for the retirement of the standalone Salesforce Maps app and Maps Live Tracking Mobile

Salesforce retired the standalone Salesforce Maps app for iPhone and Android on 31 August 2026. Reps now use the Maps tab inside the main Salesforce mobile app. On the same day Salesforce retired Maps Live Tracking Mobile, and live tracking did not move into the main app. Salesforce points to Check-In and Mileage Administration in its place, through third-party products named TripLog and Voze. Desktop Salesforce Maps is unchanged.

The article sets out three options for a field sales team. The first is to stay on Salesforce and move reps to the Maps tab in the mobile app, which suits reps who work in Salesforce all day. The second is to move to a dedicated per-user field tool such as Badger Maps, SPOTIO or Map My Customers, which suits teams where route optimisation and live mapping are central. The third is to own a field app, which the author suggests for teams that visit the same customers on a cycle and take orders and collect payments.

The author’s own product, Beatplan, is presented as the third option. It offers daily visit plans, GPS-verified check-ins with photos, order handling through dispatch and payment, cash and cheque collections, customer balances, and a manager dashboard on iPhone, Android and web. The article is explicit that it has no live location tracking, no route optimisation, no CRM deal pipeline and no Salesforce or Zendesk sync, and that dealer orders need a connection while visits, plans and payments work offline. It is sold once for US$2,900, with hosting from about US$25 a month.

The piece is disclosed as written by a person who works on the product and was produced with AI assistance. Its facts were checked against vendor pages in November 2026, and readers are advised to confirm current vendor documentation before acting.

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

Worth reading?

Releases

Trailblazer Community forums move to Slack, with read-only dates and access steps (opens in a new tab)

You will learn the timeline for the forum shutdown and Slack open beta, how to sign in with your TBID, and how groups, channels and synced content change.

  1. 15 Sep 2026: Move to Slack announced at Dreamforce
  2. October 2026: Group leaders attend workspace training
  3. 30 Oct 2026: Online forums become read-only
  4. November 2026: Slack community opens as open beta
  5. Early 2027: Accepted answers sync to community site
Key dates as the Trailblazer forums move to Slack, from announcement to web sync

The Trailblazer Community forums stopped accepting new posts on October 30, 2026, and the online community is moving to a Slack workspace that is now in open beta. Salesforce says the move is meant to support real-time conversation, help members find local Trailblazers and groups, and speed up answers through Slackbot and an Answers Agent. The full timeline runs from the September 15, 2026 announcement at Dreamforce through the November 2026 beta launch to early 2027, when accepted answers from Slack product channels begin syncing back to the community website.

The web forums now work as a read-only archive. Members can browse and search every historical discussion, and Salesforce says it will not remove any content. Joining is free: you sign in with your existing Trailblazer ID, so no paid Slack license or separate account is needed. If an employer blocks Slack, the article suggests using a personal device and the personal email tied to your TBID, or opening the workspace in a web browser.

Members who answered questions in the old forums may see a large unread count, because some forum data was synced into Slack with original authors attributed. The article gives a shortcut to clear it: open the workspace, press Shift + Esc to mark all messages as read, and confirm. Group pages stay on trailblazercommunitygroups.com, local groups gather in regional hubs such as #hub-northern-california, and global channels cover topics like Admins, Developers, Architects and Agentforce. Every channel is public, and members can request new ones after launch.

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

Worth reading?

In brief