The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Showing an Apex Collection in a Screen Flow Data Table without a Custom Object (opens in a new tab)

You will learn how to define an Apex row type, return it from an invocable action and bind it to a Screen Flow Data Table with a Unique Identifier, avoiding helper objects.

Why read this

You will also learn the current limit that inline editing is not yet supported.

  1. Define row class with @AuraEnabled fields
  2. Return list from invocable action
  3. Store output in Apex-typed collection variable
  4. Bind to Data Table with Unique Identifier
How an Apex collection reaches a Screen Flow Data Table

Since Winter ’26 (API 65.0 and later), a Screen Flow Data Table can take a collection of an Apex-defined type as its Source Collection. Choosing a field as the Unique Identifier lets the table treat each item as a record, so users can select rows and the flow can reuse them. Display and selection work now, but inline editing for these collections is still pending.

The article contrasts this with older workarounds: creating a Custom Object that mirrors the Apex class, inserting and deleting temporary records, using a Transform element, or building a custom Lightning Web Component. Each works but leaves extra metadata to maintain. The walkthrough shows a sample FxRate class with @AuraEnabled fields, an invocable GetFxRates action that wraps the list in a result class, and the flow wiring that stores the output in a collection variable and feeds it to the table.

The author advises choosing a stable, unique key such as a record Id, an ISO currency code or a business key as the Unique Identifier, and generating one in Apex if the source has none. The pattern suits currency or stock quotes from an external API, financial calculations resolved in Apex, and batch results that should not be persisted.

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

Worth reading?

Prototyping Screen Flows and record pages before building in a sandbox (opens in a new tab)

You will learn a four-step pre-build method for mapping and mocking up Lightning pages and Screen Flows with stakeholders, and when to choose Dynamic Forms over a Screen Flow.

Why read this

You will also see how to turn the approved prototype into a field dictionary and Gherkin acceptance criteria.

  1. Map the process swimlane
  2. Prototype the record page in SLDS
  3. Test visibility and edge cases live
  4. Export data dictionary and Gherkin
The four steps from discovery to a spec ready for sandbox configuration

The author opens with a familiar failure: a discovery workshop produces a requirement that is then built in a Developer Sandbox over two days, only to be reworked after a playback call. He argues that the gap is stakeholders not being able to picture how a written user story becomes a real Lightning page or Screen Flow until they see it, and that generic tools fall short. Written stories, Figma or Miro canvases, and prototyping in a sandbox each fail for Salesforce in different ways, so the prototype should stay within SLDS constraints.

The method starts with mapping the process swimlane using Universal Process Notation, identifying the trigger, decision gateways, and whether the user needs a guided wizard or persistent fields with conditional visibility. A rule of thumb is given: use Dynamic Forms with Path guidance for ongoing single-record updates with a few conditional fields, and a Guided Screen Flow for multi-step wizards, related child record creation or verification before advancing a stage. The prototype is then reviewed across four zones of the Lightning page: the Highlights Panel, Path stages with guidance text, two-column detail sections, and sidebar Related Lists.

The author then recommends testing conditional visibility and edge cases live, including negative paths, persona-based editability, and console density. Finally, the approved prototype is converted into a field-level data dictionary and Given/When/Then acceptance criteria before any sandbox configuration begins. The approach is presented as a 15-minute pre-sandbox routine, though the article is aimed mainly at admins and business analysts.

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

Worth reading?

Handling Flow errors with Fault paths, logging and notifications (opens in a new tab)

You will learn why a Flow can fail without anyone noticing, and five practices for using Fault Paths to log, notify and test failures.

Why read this

The advice is standard but practical for admins maintaining automation.

  1. Data element fails
  2. Fault Path runs
  3. Log failure record
  4. Notify admin or owner
How a failed Flow element is handled once a Fault Path is in place

A Fault Path is the branch a Flow takes when one of its elements fails, such as a record update blocked by a Validation Rule, a create that trips a duplicate rule, or a lookup that returns nothing. Without one, a Screen Flow shows the user a generic error, while a Record-Triggered Flow rolls back quietly and tells no one. The author argues that failures are easy to miss for this reason and that a missing branch is usually the cause.

The article gives five practices. Add a Fault Path to every data element, since failures often come from changes made elsewhere, such as a new Validation Rule or a permission change. Log each failure to a Custom Object, capturing the Flow name, element, record ID and the $Flow.FaultMessage value. Pair the log with a notification to an admin group or record owner so failures are seen the same day. Decide for each Flow whether a failure should stop the process or let it continue and flag the record for follow-up. Finally, test the failure paths in Flow Builder’s debug mode by feeding in data that violates a rule before each deployment.

The author also notes that a Flow can fail for different reasons depending on whether it runs in system or user context, because of Sharing Rules, field-level security or missing permissions. If a Flow fails only for some users, the run context should be checked first.

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

Worth reading?

Recommended

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?

Replicate the standard Recently Viewed List View inside a Screen Flow (opens in a new tab)

You will learn how to query the Recently Viewed object, merge its results with parent records using the Transform element, and sort the combined data for display in a Screen Flow.

Why read this

This approach replaces the missing native sorting capability in Flow Builder.

The article addresses the limitation of Flow Builder when trying to replicate the standard Recently Viewed List View, noting that direct sorting by view date is unavailable through standard Get Records elements. It introduces the Recently Viewed object as the underlying source that tracks records accessed by each user without requiring explicit user filtering.

The author demonstrates a six-step process starting with a Get Records element to fetch Recently Viewed entries filtered by the Account type. A Transform element extracts the record identifiers, which are then used in a second Get Records element to retrieve full Account data.

Because the original view date field resides outside the Account collection, another Transform element joins the two datasets using the record identifier as the key. The merged collection is subsequently ordered by the Last Viewed Date field using a Collection Sort element before being rendered in a Data Table component.

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

Worth reading?

Must-read

Winter '27 lets admins trigger Screen Flows from List Views and Related Lists (opens in a new tab)

A step-by-step setup for the Winter '27 feature that passes the records a user selects in a List View or Related List into a Screen Flow.

  1. Build Screen Flow with ids variable
  2. Create Flow action on the object
  3. Add to List View Button Layout
  4. Add to Dynamic Related List – Single
Setup for running a Screen Flow on selected records

Starting in Winter ’27, users can select several records in a List View or a Related List and hand them to a Screen Flow that opens in a modal. The article treats it as an overlooked part of a large release because it lets admins build mass actions without code.

The setup has one detail that is easy to miss. The flow needs a text collection variable named ids, in lowercase, marked as available for input. The selected record Ids arrive in that variable. The example flow gets the matching Contacts, shows them in an editable Data Table on a screen, and writes the edits back with an Update Records element, with fault paths on the data elements.

To expose it, create an action of type Flow on the object and add it to the List View Button Layout under the Lightning Experience List View actions. For Related Lists, create the same kind of action, then add it to a Dynamic Related List – Single component on the parent’s Lightning Record Page.

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

Worth reading?