The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

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?

Must-read

Salesforce delivers long-awaited Flow actions, List View permissions, and User history tracking (opens in a new tab)

Readers will learn how to configure mass Screen Flow actions in List View layouts, restrict List View sharing without granting broad permissions, and enable Field History Tracking on the User object.

Delivered IdeaExchange Features

  • Flow Quick Actions in List Views
  • Manage Shared List Views Permission
  • Inline Editing on List Views
  • Field History Tracking for Users
  • Restart Superbadge Progress
Five long-requested IdeaExchange ideas finally shipped in recent releases

The latest IdeaExchange updates highlight several features delivered in Winter ’27 and Summer ’26 that resolve long-standing administrative limitations. Administrators can now execute Screen Flow actions against multiple records selected in List View layouts or Related Lists by passing record identifiers into a text collection variable, eliminating the need for custom components or workarounds.

A new Manage Shared List Views permission replaces the broad Manage Public List Views requirement, allowing targeted sharing without exposing all public views across the organization. Winter ’27 also removes the restriction preventing inline editing in List Views containing multiple record types, though administrators must manually activate the setting in User Interface Settings and test it carefully due to varying Validation Rules and picklist values.

Field History Tracking is now available for the User object, monitoring up to twenty fields such as profile, role, and manager changes for eighteen months. The article also notes that Trailhead Superbadges can now be restarted after completion, supporting skill reinforcement rather than single-use certification, while additional roadmap items like dark mode and Opportunity restriction rules remain in development.

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

Worth reading?

Recommended

Winter '27 release brings user history tracking and manual share retention (opens in a new tab)

Readers will learn how to enable native field history tracking on the User object, preserve manual record shares during ownership transfers, and leverage new Lightning App Builder layout controls without writing code.

Why read this

They will also discover diagnostic tools for monitoring Custom Field indexing and query frequency to reduce technical debt.

The Winter ’27 release makes field history tracking generally available for the User object, allowing administrators to monitor up to twenty fields such as profile, role, and active status directly through the Object Manager. An org-wide toggle under Sharing Settings now prevents manual record shares from being deleted when a record owner changes, which helps maintain collaboration during territory restructures.

The update expands Lightning App Builder capabilities by adding dynamic sorting for Related Lists based on formulas or lookups, conditional section headers that show or hide accordion groups, and scheduling tools for in-app prompts to prevent user fatigue. These layout enhancements align with SLDS 2 Cosmos accessibility standards and require no custom components.

Administrators can now view index status reports for Custom Fields within the Performance Metrics dashboard to troubleshoot slow SOQL queries and report timeouts. Object Manager also displays last modified dates and query frequency for each Custom Field, enabling safer and faster cleanup of unused fields before deprecation.

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

Worth reading?

Salesforce Winter '27 brings Flow testing, bulk screen actions, and higher heap limits (opens in a new tab)

Readers will learn how to implement the new Flow Test Mode, process multiple records via List Views, and adjust to increased Apex heap limits and updated REST API versioning without manual tracking.

The release introduces Test Mode for Flow Builder, enabling repeatable testing with assertions and mock outputs for external callouts. Screen Flows launched from List Views or Related Lists can now process multiple selected records by accepting a lowercase ids collection variable. Reactive Formulas allow Conditional Visibility to evaluate same-screen inputs instantly, while new save-time validation catches missing Required Fields and character limit breaches before runtime.

Logic handling gains Split by Field Value and Split by Date elements, which create automatic branches but do not fully replace Decision elements. Navigation improves through an Unused Resources filter, Element Grouping, and an Edit History panel. Security receives a User Context option that enforces running user permissions, and an org-wide toggle preserves Manual Shares when record ownership changes.

Synchronous Apex transactions now support a 10 megabyte heap limit, while asynchronous transactions reach 25 megabytes, with a transition setting available to manage the shift. List View inline editing expands to include off-page layout fields and mixed Record Types. Integrations may use latest for REST API versioning, and Field History Tracking becomes generally available for the User object.

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

Also told by Salesforce Ben on YouTube (opens in a new tab)

Worth reading?