> 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

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

**Release Date: August 28, 2026**

{% columns %}
{% column %}

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

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

### Record Grid

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

Compare records side by side on a flow screen. The Record Grid turns the usual table on its side: one column per record, headed by whatever identifies it, and the fields you pick shown as rows. Point it at an in-flow resource such as a Get Records collection or a Data Table selection, and a reviewer can read three submissions against each other without leaving the screen. Supports download, field help text, a frozen top row and left column, and configurable cell sizing.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FlG8USZN6yRgChDL6PYv2%2Faugust-28-2026-record-grid-inline.png?alt=media" alt=""><figcaption></figcaption></figure>

**Documentation:** [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/record-grid)

### Heatmap & Treemap Charts

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

A new Grids family joins the chart library. The Heatmap plots a category on each axis and colors every cell by a numeric measure, with a sequential color scale and a matching legend, so a busy month or an underperforming region shows up as a block of color. The Treemap shows nested rectangles sized by value. Both use the same data model and color configuration as the rest of the chart family.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FjUYA4xUz4ZZkBOmMfw5i%2Faugust-28-2026-treemap-inline.png?alt=media" alt=""><figcaption></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chart) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/chart)

***

## Improvements

### Charts

**Custom Brand Colors**

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

Charts are no longer limited to the 15 predefined palettes. A new **Custom Palette** property takes a list of your own hex colors and overrides the preset, so a dashboard can follow your brand book exactly. Each Flat Gauge tier can carry its own color too, so four gauges on one screen can each read differently.

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chart) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/chart)

### Gauges

**Redesigned Radial Gauge and New Flat Gauge Types**

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

The Radial Gauge has been redesigned around a large centered value with a filled progress arc, and it gains two controls: the indicator can be a needle or a circle, and the tick values along the arc can be hidden for a cleaner read. The Flat Gauge gains two display types alongside Continuous: **Discrete**, which splits the track into a set number of steps, and **Tiered**, where you define each tier yourself with its own label, share of the range, and color.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2Fb65GRsv1WsFRhvTD60cp%2Faugust-28-2026-flat-gauge-tiers-inline.png?alt=media" alt=""><figcaption></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chart) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/chart)

### Kanban

**Reorder Cards, Swimlane Totals, and Deeper Fields**

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

Cards can now be dragged up and down inside a column to sequence them by priority without changing their status, the same drag-to-reorder the List component already offers. Swimlane headers can show a configurable total next to the record count, matching the aggregate already available on column headers. Card fields, filters and sorting can also reach fields on related and parent objects several levels deep, so a board can group on an account owner without a formula field standing in for it.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2F2bumwg0qBE17UGuQ9UTS%2Faugust-28-2026-kanban-swimlane-totals-inline.png?alt=media" alt=""><figcaption></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/kanban) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/kanban) · [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-kanban)

### Map

**Several Records at One Address**

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

Several accounts registered at one shared office building used to collapse into a single marker, and only the topmost one answered a click. Every record at those coordinates is now reachable: page through them from the marker popup, without editing any record's real address to pull them apart.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FQZAgnnIUfDtwHDm6xdWH%2Faugust-28-2026-map-same-address-inline.png?alt=media" alt=""><figcaption></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/map) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/map) · [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-map)

### Record Detail

**Fields Scoped to a Record Type**

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

Custom Layout fields can now be limited to the record types they apply to. One Record Detail can serve an object whose record types share most of their fields but differ in a few, so a form that changes slightly by region or business line no longer needs a separate layout for each.

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/record-detail) · [Flow Components](https://docs.avonnicomponents.com/flow/flow-components/record-detail) · [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-record-detail)

### Chat

**Reply to a Message**

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

You can now reply to a specific message instead of to the conversation. The reply carries a quoted preview of the original showing who replied to whom, and clicking that quote jumps back to the message it answers.

<figure><img src="https://308846571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKhdnlWvAsVCp5hWw4Mfd%2Fuploads%2FQDJW5L1KSEcx4TrhCv4M%2Faugust-28-2026-chat-reply-inline.png?alt=media" alt=""><figcaption></figcaption></figure>

**Documentation:** [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/components/chat)

### Scheduler

**Custom Event Popover**

<mark style="background-color:green;">**`LWC Components`**</mark>

The event detail popover can now render your own markup instead of the default field list. Compose the Scheduler in your own Lightning Web Component and fill its `event-detail-popover` slot: a contact photo, a status badge and an action button where a list of display fields used to be.

**Documentation:** [Scheduler for LWC](https://docs.avonnicomponents.com/lwc-components/data-driven-components/scheduler)

### Picklist Values Editor

**Clearer Popover Placement**

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

The picklist values editor now opens its popover beside the item you are editing, matching the tree property editor, so the rest of the list stays visible while you work.

***

## Bug Fixes

### Data Table

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

* **Selection limit across pages**: the maximum row selection is now enforced across pages. The header select-all used to add up to the maximum on every page, and row checkboxes stayed clickable past the limit after a page change, so a flow could receive more records than configured.
* **Lookup on the record's own Id**: a lookup column mapped to the record's own Id no longer renders blank in query mode.
* **Export after Select All Items**: exporting after Select All Items now returns the same set as exporting an individual selection.

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

* **Currency Cell Attributes**: Currency columns now show their Cell Attributes in the Dynamic Component Builder, as they already did in Flow and Experience.
* **Field Name toggles**: the Field Name toggle on SLDS Cell Class, Icon Name and Icon Position opens the field picker again, on every column.

### Tree Grid

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

* **Linkify columns**: columns with Linkify ticked now render as links to the record instead of plain text, for the Text, Record Picker and Lookup column types alike.

### Charts

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

* **Missing measure field**: a chart whose measure field is not available on the object for the running user now reports an error instead of rendering blank with nothing to explain it.
* **Count measure**: the Count measure no longer requires a number-typed field.

### Pivot Table

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

* **Lookup name filter**: a filter on a lookup's Name now matches records whose name runs to more than a first and last name. A client with a middle name or a suffix used to come back as "No results" even though the filter itself had counted it.

### Field

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

* **Blank numbers**: a blank number, currency or percent field now renders blank instead of `0` or `$0`, so an empty value can be told apart from a real zero.

### Property and Filter Editors

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

* **Relationship fields**: relationship fields are available again in the filter and condition picker, so conditions can be built on a field of a related record, and conditions saved earlier load with their labels intact.
* **Nested relationship fields**: nested relationship fields now show their field name the first time they load.
* **Mapped value mode**: the value mode menu no longer offers a Mapped option on properties where no resource could ever be selected.

### Progress Indicator

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

* **Chained step actions**: when several Step Click interactions are chained on a path, a failure now stops the chain. A record update rejected by a validation rule no longer reports "Your changes are saved."

### Navigation

<mark style="background-color:orange;">**`Experience Sites Components`**</mark>

* **Sub items**: the navigation menu data source now builds sub items correctly, so a parent item with children shows its dropdown again, like the standard Salesforce navigation bar.

**Documentation:** [Experience Sites](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-navigation)

***

## Installation & Update

{% 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><strong>v1.27</strong></td></tr><tr><td><strong>Install in Sandbox</strong></td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000Fu57YAC"><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=04tOJ000000Fu57YAC"><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.32**                                                                                          |
| **Install in Sandbox**    | [**Install →**](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tak000000eAVJAA2)  |
| **Install in Production** | [**Install →**](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000eAVJAA2) |

***

#### **LWC Components**

Standalone package with the Avonni base component library for developers building custom Lightning Web Components.

| Detail                    | Value                                                                                              |
| ------------------------- | -------------------------------------------------------------------------------------------------- |
| **Includes**              | LWC Components                                                                                     |
| **Version**               | **v1.11**                                                                                          |
| **Install in Sandbox**    | [**Install →**](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000Fu3VYAS)  |
| **Install in Production** | [**Install →**](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000Fu3VYAS) |

***

#### **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><strong>v1.54</strong></td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000Fu6jYAC"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tOJ000000Fu6jYAC"><strong>Production</strong></a></td></tr><tr><td>Experience Sites Components (standalone)</td><td><code>avcmpbuilder</code></td><td>n/a</td><td><a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04tak000000UhFdAAK&#x26;isdtp=p1"><strong>Sandbox</strong></a> / <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04tak000000UhFdAAK&#x26;isdtp=p1"><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/whats-new-at-avonni.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.