For the complete documentation index, see llms.txt. This page is also available as Markdown.

What's New At Avonni

Stay up to date with the latest features, improvements, and fixes across all Avonni component suites for Salesforce.

Release Date: May 22, 2026


Improvements

Experience Site Variables – Map Into Dynamic Components

Dynamic Components | Experience Sites Components

Experience Site binding variables from reactive components can now be mapped as input into Dynamic Components. This makes it possible to build dashboard-style Home pages where selecting a record dynamically updates other components with the relevant data.

Interactions – Execute Flow & Invoke Agent on All Components

Dynamic Components | Flow Components

The Execute Flow and Invoke Agent interactions are now available across all components, giving a consistent way to trigger flows and agents from anywhere on the canvas.

Filter – Cascading Filter Values

Dynamic Components | Flow Components | Experience Sites Components

The Filter component now supports cascading (dependent) filter values. When a filter is applied, the options in other filters are automatically narrowed to only the values that match the current selection.

Pivot Table – Group Date Fields by Year, Month, and More

Dynamic Components

The Pivot Table now lets you group date fields by year, month, and other intervals, consistent with the grouping options already available in the Chart component.

Dynamic Components – Faster First Load

Dynamic Components

Improved the first-load performance of Dynamic Components. Components that previously took a long time to appear on the first load of the day now load significantly faster.

Chat – Time Break Option

Dynamic Components

The Chat component now includes an option to enable time breaks, which automatically insert dividers between messages to organize a conversation by date.


Bug Fixes

Data Table

Dynamic Components | Flow Components

  • Group By – Alignment Issue with Row Number and Checkbox Columns: Fixed an alignment issue that occurred when the row number column and checkbox column were displayed together in a grouped Data Table.

Kanban

Dynamic Components

  • Filtering in Variable Mode: Fixed an issue where applying filters in Variable Mode had no effect on the items displayed.

  • Cards Showing Empty Boxes: Fixed a bug where Kanban cards loaded empty when running in the app, even though all item fields displayed correctly in preview mode.

Dynamic Component Builder

Dynamic Components

  • Avatar Initials Background: Fixed an issue where the background was not set properly for the Avatar example when displaying initials.

  • Scheduler – Search Value in Toolbar: Fixed an issue with the search value behavior in the Scheduler toolbar.

  • Global Header – Flickering on Salesforce Mobile: Fixed a bug where a header inside a Dynamic Component with many filters in a popover would flicker on Salesforce Mobile. Desktop was unaffected.

Flow Screen Components

Dynamic Components

  • Merge Fields in Semi-Join Sub-Conditions: Fixed an issue where flow variables and merge fields could not be used in the value of a Semi-Join or Anti-Join sub-condition. Merge fields are now accepted in the inner sub-condition.

  • Flow Filter Query – Error When Selecting IN Filters: Fixed a "Maximum Stack Size Exceeded" error that occurred when selecting IN filters in Flow Screen Components.

  • List Query Losing Filter After Previous: Fixed an issue where a List component query stopped honoring its filters after navigating forward and then pressing Previous.

  • Semi-Join Filters Using IN: Fixed a bug where Semi-Join filters using IN did not work as expected in Flow Screen Components.

  • Flow Combobox – Multi-Select Capped at Dropdown Length: Fixed a bug where a multi-select Combobox with "Hide Options Until Search" enabled could not select more items than the configured Dropdown Length. The configured maximum selection is now respected.


Important

The full bundle is available on AppExchange. Use this if you're installing Avonni for the first time or want all components in a single package.

Detail
Value

Includes

Dynamic Components, Experience Sites Components, App Builder Components

Namespace

avxp

Version

v1.22

Install in Sandbox

Install in Production


Flow Screen Components

Standalone package for Salesforce Flow Builder. Install this if you build screen flows and want Avonni's flow-specific components.

Detail
Value

Includes

Flow Screen Components

Version

v6.26

Install in Sandbox

Install in Production


Legacy Packages

For existing customers using one of the older standalone packages. Not available on AppExchange. If you're starting fresh, install Avonni Components (the bundle above) instead.

Package
Namespace
Version
Install

Dynamic Components (standalone)

avdynamic

v1.49

Experience Sites Components (standalone)

avcmpbuilder


Previous Release - May 14, 2026

May 14, 2026

Previous Release

New Components

Dynamic Components

A new Menu Navigation Container component is now available in the Dynamic Component Builder. Each menu item has its own container — drop components directly inside, and the active item handles what's shown. No more visibility rules to switch views.

Image List

Flow Components

The Image List component is now available as a Flow Screen component. Customers can now display and filter large collections of images directly within Salesforce Flow experiences.


Improvements

Dynamic Component Builder

New Component Creation Modal

Dynamic Components

A redesigned "New Component" modal is now displayed when creating a Dynamic Component. It includes standard and custom templates, making it easier to get started quickly.

Standard Component Templates

Dynamic Components

A new set of standard templates is available when creating a Dynamic Component, including Dynamic Related Views, Dynamic Views, Calendar standalone, and more. Templates pre-configure layouts and views to accelerate component setup.

Resources

Variables – JSON Data Type 🔥

Dynamic Components

Variables now support a JSON data type, so a single Variable can hold an entire record, a list of records, or any nested structure — instead of flattening everything into separate text and number variables.

What this unlocks for admins:

  • One variable instead of fifteen. Capture a full Flow output, an Agentforce response, or a multi-screen wizard's data in a single JSON Variable.

  • Show structured results without code. Drop a Data Table, Kanban, List, or Map, point it at a JSON Collection, and render Flow or Agentforce results directly — no custom object, no Apex.

  • Mock data while you wait on dev. Pre-fill a JSON Variable with the expected shape, build your UI on top of it, then swap in the real source when it's ready.

A new Structure Editor lets you define the shape — fields, types, nesting — directly in the Builder, and reference any path with {!myVariable.field.subfield}.

In practice — Sales Field Visit Optimization

A rep has 15+ accounts to visit this week. Instead of spending 30 minutes planning every morning, they click a button: an Agentforce agent reads their territory, prioritizes accounts, and optimizes the route. The structured response lands in one JSON Variable that feeds an interactive Map and a stop-by-stop List on the same page.

Interactions

On Load – Run Conditionally

Dynamic Components

On Load interactions can now be configured to run conditionally based on a rule, similar to Component Visibility. This is especially useful when combined with interactions like Invoke Agentforce Agent — for example, to run only when a summary field is not yet populated.

Update/Upsert Record – Enter Data Manually

Dynamic Components

The Update/Upsert Record interaction now supports a manual data-entry mode, allowing field values to be defined directly in the interaction configuration without requiring a flow variable.

Refresh Query – Select Component to Refresh

Dynamic Components

The Refresh Query interaction now lets users select which component to refresh, rather than always refreshing the current one. A new Component to refresh multi-select field lists all eligible components, with a "Current Component" default option.


Last updated

Was this helpful?