> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/changelog/whats-new-at-avonni.md).

# What's New At Avonni

#### Release Date: May 22, 2026

{% columns %}
{% column %}

### [Installation & Update Links](#installation-and-update-links-1)

{% endcolumn %}

{% column %}

<p align="right"><a href="https://dashboard.mailerlite.com/forms/808392/134910842135119740/share" class="button primary" data-icon="bell">Subscribe for Updates</a></p>
{% endcolumn %}
{% endcolumns %}

***

## Improvements

### Experience Site Variables – Map Into Dynamic Components

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:cyan;">**`Experience Sites Components`**</mark>

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

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

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

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark> | <mark style="background-color:cyan;">**`Experience Sites Components`**</mark>

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

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

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

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

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

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

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

<mark style="background-color:blue;">**`Dynamic Components`**</mark> | <mark style="background-color:violet;">**`Flow Components`**</mark>

* **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

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

* **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

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

* **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

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

* **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.

***

## Installation & Update Links

{% hint style="danger" %}

#### Important

Because each release can introduce important architectural or behavioral changes, **we strongly recommend first installing it in a sandbox environment to validate** the updates and confirm that all your existing processes still work as expected before deploying to production
{% endhint %}

### **⭐ Avonni Experience Components (recommended)**

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.

<table><thead><tr><th width="213.56597900390625">Detail</th><th>Value</th></tr></thead><tbody><tr><td><strong>Includes</strong></td><td>Dynamic Components, Experience Sites Components, App Builder Components</td></tr><tr><td><strong>Namespace</strong></td><td><code>avxp</code></td></tr><tr><td><strong>Version</strong></td><td>v1.22</td></tr><tr><td><strong>Install in Sandbox</strong></td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000E7jBYAS"><strong>Install →</strong></a></td></tr><tr><td><strong>Install in Production</strong></td><td><a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000E7jBYAS"><strong>Install →</strong></a></td></tr></tbody></table>

***

### **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 →**](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tak000000SwnR)  |
| **Install in Production** | [**Install →**](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000SwnR) |

***

### **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.

<table><thead><tr><th>Package</th><th width="142.77691650390625">Namespace</th><th>Version</th><th>Install</th></tr></thead><tbody><tr><td>Dynamic Components (standalone)</td><td><code>avdynamic</code></td><td>v1.49</td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000E7hZYAS"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000E7hZYAS"><strong>Production</strong></a></td></tr><tr><td>Experience Sites Components (standalone)</td><td><code>avcmpbuilder</code></td><td>—</td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tak000000SwnR"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000SwnR"><strong>Production</strong></a></td></tr></tbody></table>

***

{% hint style="success" %}

#### Previous Release - **May 14, 2026**

Headlined by JSON Variables, two new components, four interaction upgrades, expanded Kanban, and 35+ bug fixes.

:arrow\_down:
{% endhint %}

{% content-ref url="/pages/AWdkijJdMnq1ha9uKgpY" %}
[May 14, 2026](/changelog/archives/may-14-2026.md)
{% endcontent-ref %}

***

## Previous Release

### New Components

#### Menu Navigation Container

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

A new [**Menu Navigation Container**](/dynamic-components/components/navigation-container.md) 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.

<figure><img src="/files/gNcs5se02yuxpUi0uMxl" alt=""><figcaption></figcaption></figure>

#### Image List

<mark style="background-color:violet;">**`Flow Components`**</mark>

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**

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

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.

<figure><img src="/files/SwZf20FnpuBrnSjaffbI" alt=""><figcaption></figcaption></figure>

**Standard Component Templates**

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

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 🔥**

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

Variables now support a [**JSON data type**](/dynamic-components/component-builder/resources/variable.md#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.

<figure><img src="/files/jJSEMLuz7nOGHgL2xDSI" alt=""><figcaption></figcaption></figure>

### Interactions

#### On Load – Run Conditionally

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

On Load interactions can now be configured to [**run conditionally**](/dynamic-components/component-builder/on-load-interaction.md#when-to-execute-interaction) 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.

<figure><img src="/files/OkLkDom0zWr31QvfzKqO" alt=""><figcaption></figcaption></figure>

#### Update/Upsert Record – Enter Data Manually

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

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

<mark style="background-color:blue;">**`Dynamic Components`**</mark>

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.

<figure><img src="/files/ol7zYaj37eMhvPkaskJ2" alt=""><figcaption></figcaption></figure>

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.avonnicomponents.com/changelog/whats-new-at-avonni.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.