Query

Overview

The Query Data Source enables Avonni Data Components—such as Data Table, List, Gallery, and Map—to dynamically retrieve and display Salesforce record data on Experience Cloud sites.

This data source is designed for situations where content must stay in sync with Salesforce data and respond dynamically to user interactions on the page.

---

What is the Avonni Query Data Source?

The Avonni Query Data Source connects Avonni components directly to Salesforce objects via a configurable query, similar in concept to SOQL but built visually.

In an Experience Cloud context, it enables:

• Dynamic data retrieval from Salesforce records

• Reactive behavior between components on the same page

---

Creating a query

Queries are created directly from an Avonni component.

To create a new Query:

1. Select an Avonni Data Component (for example, a Data Table or List) in Experience Builder

2. In the component’s properties panel, open the Data Source section

3. Select Query as the data source

4. Configure the query fields, filters, and options

---

Filtering data

Configuring query filters

Filters allow you to control which Salesforce records are returned by the query, similar to a WHERE clause in SOQL.

Filters are configured directly in the query editor and apply to all components using that query.

---

Types of filters

Static filters

Static filters use fixed values defined at configuration time.

Example:

• Field: Location

• Operator: equals

• Value: New York

Static filters do not change unless the query is edited.

---

Reactive queries

What are reactive queries?

Reactive queries enable Avonni components on an Experience Cloud page to automatically update in response to user interactions or changes in other components.

This enables highly dynamic, interactive pages without page reloads or custom code.

Learn More

---

When to use the Query Data Source

Use the Query Data Source when:

• Data must stay synchronized with Salesforce records

• Content must react to user interactions

• Multiple components need to share the same dataset

• Filtering and grouping logic is required

For static or editorial content, consider using Manual or CMS Collection data sources instead.