> 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/archives/may-14-2026.md).

# May 14, 2026

#### Release Date: May 14, 2026

This release is headlined by **JSON Variables** — one Variable can now hold a full record, collection, or nested object, and feed it straight into any data-aware component. It also ships two new components, a redesigned Component Builder save-and-creation flow, four interaction upgrades, expanded Kanban, and 35+ bug fixes.

{% 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 %}

***

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

#### Improved Save Experience

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

The save experience in the Dynamic Component Builder has been significantly improved. A **"Saving…" message** now appears instead of a full-page spinner, allowing users to continue editing without interruption. Creating a new component now opens the builder in empty mode immediately — the settings dialog appears on the first save, eliminating unnecessary wait times.

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

#### Selection Components – Initialize Output Variables on Load

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

For Dynamic Components that support selection and default values (e.g. Combobox, Button Menu), the **output variables related to selection** are now initialized on load, without requiring any user interaction.

### Kanban

#### Infinite Loading per Column

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

The **Kanban** component now supports **infinite scrolling per column**. As users scroll to the bottom of a column, additional records are loaded automatically — consistent with how the Data Table handles large datasets.

#### Display Empty and Undefined Subgroups

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

The Kanban component now includes two new options to control subgroup visibility: **Hide Undefined Group** and **Show Empty Groups**. These options mirror the equivalent behavior available in the Data Table.

### Data & Visualization

#### Pivot Table – Detail Rows & Inline Edit

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

The **Pivot Table** component now supports [**drill-down detail rows**](/dynamic-components/components/pivot-table.md#detail-rows-and-inline-edit) when clicking on a cell, showing the underlying records that make up an aggregated value. Inline editing is also supported within these detail rows.

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

#### Data Components – Styling Hook for Selected Item

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

A new **styling hook** is available on repeater-based data components (List, Repeater) to apply a background color to the currently selected item, making it visually clear which item is active.

#### Datatable – Column Property "Map to Field Name" in Manual Mode

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

When using a **Datatable** with a manual data source (JSON collection), column type-specific properties like **Badge variant** can now be mapped to a field from the data, working consistently with the Salesforce object data source mode.

#### Data Table – File Upload Triggers a Sub Flow After Upload

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

The **File Upload column** in the Flow Data Table now supports triggering an interaction upon file upload. You can pass the Content Document ID and other metadata directly into a Sub Flow, turning multi-step upload workflows into a single action.

#### Data Table – Group By Exported with Formatted Report

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

When exporting a Data Table that uses **Group By**, the export now preserves the group structure and produces a properly formatted report that matches the grouped view seen on screen.

#### Map – Leaflet Custom Tile Layer

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

The **Dynamic Component Map** now supports a custom Tile Layer option for Leaflet maps, consistent with what was already available in the Flow Map component. Organizations can use their own map tile provider.

#### JSON Resource – Field Support

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

JSON resource collections now support **field mapping**. In components like the List, individual fields from a JSON resource can be selected and displayed in the item's fields section.

#### Timeline – Improved Utility Icon Display

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

Utility icons used as avatar icons in the **Timeline** component now display cleanly against the timeline bar, with a proper background to prevent them from appearing transparent or blending in.

### Record & Input Components

#### Record Detail – Custom Layout

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

The **Record Detail** component now supports a **custom field layout**, allowing users to define exactly which fields to display and in what order, without relying on the standard or compact page layout.

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

#### Input Components – Reactive Variable Binding

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

**Input components** now update their assigned variable values reactively. There is no longer a need to configure a separate assignment interaction — the variable stays in sync automatically as the user types.

#### Combobox – Tooltip on Truncated Options

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

The **Combobox** now displays a tooltip when an option's label is truncated, allowing users to see the full text on hover.

### Filters

#### Hide Empty Option for Picklist

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

When **Use Record Picklist Values** is enabled and there are no blank records, the **"Empty" filter option** is now hidden automatically, keeping the filter UI clean and relevant.

### Layout & Containers

#### LWC Container – Size and Full Height Options

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

The **LWC Container** component now includes a **Size** section (Width, Height, Min/Max Width, Min/Max Height, Overflow) and a **Full Height** shortcut in the Style tab, matching the standard Container component's existing behavior.

***

## Bug Fixes

### Dynamic Component Builder

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

* **Open Dynamic Component Dialog – Endless Loading Spinner**: Fixed an urgent regression where any trigger wired to an "Open Dynamic Component Dialog" interaction displayed an endless loading spinner. The modal header appeared but the inner Dynamic Component body never loaded.
* **Button Menu – All Actions Triggered Instead of One**: Fixed an urgent issue where clicking any single item in a Button Menu (Action component) was triggering all actions in the menu instead of only the selected one. This regression appeared after a Sandbox upgrade.
* **Property Editor – Lookup Fields Display Wrong Object Fields**: Fixed a bug where selecting a relationship (lookup) field was displaying the fields of the source object instead of the related object's fields.
* **Property Editor – Data Table Filter Cannot Select Relationship Field**: Fixed an issue where clicking a relationship field in the Data Table filter dropdown was showing source object fields instead of child/related object fields.
* **Property Editor – Next Interactions Label Not Computing Properly**: Fixed an issue where the label for a Next Interaction was not displaying the correct computed value.
* **Save Button Stays Disabled After Undo**: Fixed a bug where making a change and then undoing it left the Save button disabled, even when changes were still pending.
* **Dynamic Component List View – Content Not Updating Properly**: Fixed a navigation issue where switching between folders, the "Created By Me" section, and the "Archived" section did not update the content correctly.
* **Left Panel Structure – Container Components Not Clickable**: Fixed an issue where dcTabbedContainer and dcLayout containers were incorrectly becoming clickable in the left panel structure.
* **On Load Interaction – $Component Variables Not Resolved**: Fixed an intermittent issue where an On Load interaction could fire before `$Component` context variables (such as Record ID) were fully resolved, resulting in flows receiving null values.
* **Custom Permission Not Evaluated Correctly**: Fixed a bug where Custom Permissions assigned to a user were being evaluated as `false` inside Dynamic Components, preventing visibility rules from working as expected.

### Data Table

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

* **Clickable Row Not Working**: Fixed an issue where the Clickable Row feature was not correctly selecting a single row at a time.
* **Checkbox Button Column Cannot Be Unchecked**: Fixed a bug where a checkbox button column could be checked but not unchecked. Additionally, in grouped rows, checking one checkbox caused the other checkboxes to disappear.
* **Group By Header Background Grey in SLDS2**: Fixed the Group By header background color, which was incorrectly rendering in grey instead of white when SLDS2 styling is active.

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

* **Lookup Fields in Variable Mode**: Fixed incorrect mapping of lookup fields when the Data Table operates in variable mode and receives records from another component.
* **Property Editor – Source Field Loading Wrong Fields**: Fixed an issue in the Property Editor where lookup fields in the source field selector were loading incorrect fields.
* **Missing Margin Between Search Bar and Header Title (Fill Mode)**: Fixed missing spacing between the search bar and the header title when the search bar is set to fill mode.

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

* **FSC Data Table – Group By Fails to Load Records**: Fixed an urgent issue where the Data Table with Group By enabled failed to load records on initial page load, particularly noticeable on slower connections.
* **FSC Datatable – Unwanted Border Line with Pagination Enabled**: Fixed a visual issue where an unwanted border appeared below the pagination controls when pagination was enabled.

### Repeater & List

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

* **Repeater – Visibility Rules on currentRecord / clickedRecord**: Fixed visibility rules comparing `currentRecord` or `clickedRecord` in a Repeater, which were previously only working on the last item in the list.
* **Repeatable – No Results Shown Unexpectedly**: Fixed a regression where the Repeatable component was showing a "No Results" message even when data was present.

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

* **FSC List – Reorder Throws Data Type Error on Navigation**: Fixed a data type error thrown when reordering items in the FSC List component and navigating to the next flow screen.

### Calendar & Layout

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

* **Calendar – Context Menu Action Passing Literal `{{Record.Id}}`**: Fixed a bug where clicking a context menu action on a calendar event was passing the literal string `{{Record.Id}}` in the URL instead of the actual record ID.
* **Calendar – Month View Renders Too Small When Deployed**: Fixed an issue where the Calendar component, set to Month view and Calendar display mode, rendered at an unexpectedly small size on live pages. A minimum height is now enforced.
* **Layout – Nested Layout Not Responsive**: Fixed an issue where a Layout component placed inside another Layout was not responding correctly to responsive breakpoints.
* **Timeline – Vertical Line Off-Center with Action Icons**: Fixed a visual issue in the Timeline component where the vertical line shifted off-center when action-type icons were used.

### Query & Filters

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

* **Reactive Query Formula – Issues with Some Scenarios**: Fixed multiple scenarios where reactive query formulas were not evaluating correctly: initial load was showing stale data, and selection changes were not always updating the query as expected.
* **Query – Complex Formula Filter Ignored on First Selection**: Fixed an issue where a query filter built by combining values from multiple Comboboxes in a formula was being ignored the first time a value was selected.
* **Date Filter Displayed as Popover When Only One Date Filter**: Fixed incorrect display behavior where a single date filter was showing as a popover instead of inline.

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

* **Query Filters – IN Condition with Variable in OR Group Disappears After Save**: Fixed a bug where a query filter using an IN condition mapped to a variable inside an OR group would disappear after saving and reopening the query configuration.

### Kanban

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

* **Lookup Fields Not Resolving in Card Title, Caption, Description, and Image**: Fixed a bug where binding a card's title, caption, description, or image to a relationship field (e.g. a lookup) rendered empty on the Dynamic Kanban. Card body fields were unaffected.

### Map

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

* **Map – Typo in Selected Value Attribute**: Fixed a label typo in the Map component's `selectedMarkerSObjectValue` attribute in the Dynamic Component property editor.

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

* **Flow Map – Search Query Error with Custom Lookup Fields**: Fixed a malformed SOQL query error triggered by the search feature on the Flow Map when the map was configured with custom lookup fields.
* **Flow Map – Leaflet Query Limit Removed**: Removed a hardcoded 1,000-record limit on Leaflet map queries in the Flow Map component. This limit was originally introduced to improve Google Maps performance, but it does not apply to Leaflet.

### UI Components

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

* **Avatar – Circle Variant Cuts the Icon**: Fixed a visual issue where the Avatar component's circle variant was clipping the displayed icon.
* **Avonni Illustration – Styling Hooks Review**: Reviewed and corrected the styling hooks available on the Avonni Illustration component to ensure all CSS custom properties apply as expected.

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

* **Activity Timeline Horizontal – Default Icon Not Displayed**: Fixed a bug where a defined icon name was not being applied to items in the Activity Timeline Horizontal component.

### Flow Screen Components

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

* **FSC Metric – Query Filters Not Saving Consistently**: Fixed an intermittent issue where query filters set on the Metric component in Flow Builder were not always persisted after navigating away and returning.
* **Flow Builder – Property Editor Sync Issues**: Fixed several property editor bugs in the Flow Builder caused by a sync gap between the Dynamic and Flow repositories, including lookup field loading and header action interactions.
* **FSC – Apex Action SObject Collection Join**: Fixed configuration issues with the Apex Action SObject Collection Join, which was returning null values due to a setup problem.
* **Flow Combobox – Multipicklist Required Validation with Max/Min Selection**: Fixed two issues with the Flow Combobox in multi-picklist mode when Max/Min selected item values are configured: the Required setting was not respected, and navigating to the next screen with no values selected caused an error.
* **Combobox – Dropdown Clipped by Flow Dialog Modal**: Fixed an issue where the Combobox dropdown was being clipped by the modal footer when used inside a Flow dialog.

***

## 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.48</td></tr><tr><td><strong>Install in Sandbox</strong></td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000DxzxYAC"><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=04tOJ000000DxzxYAC"><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.25                                                                                                     |
| **Install in Sandbox**    | [**Install →**](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tak000000RxvF\&isdtp=p1)  |
| **Install in Production** | [**Install →**](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000RxvF\&isdtp=p1) |

***

### **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.21</td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000DxyLYAS"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000DxyLYAS"><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=04tak000000RxvFAAS"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000RxvFAAS"><strong>Production</strong></a></td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/changelog/archives/may-14-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.