Manual
Overview
The Manual Data Source is the simplest way to provide data to Avonni Data Components on a Salesforce Experience Cloud site. It allows site builders to define the data directly in the component configuration within Experience Builder, without relying on Salesforce records, CMS content, or external data sources.
This approach gives you complete control over what is displayed on a specific page and is especially useful for static or page-specific content.
How it works
Component configuration in Experience Builder
When adding or editing an Avonni Data Component (such as a List, Data Table, or Carousel) in Experience Builder, you’ll find a Data Source section in the component properties panel.
Select Manual as the data source.
Data input
Once selected, the component provides a structured, user-friendly input interface that lets you enter data directly in Experience Builder.
Depending on the component, this typically takes the form of:
A table-like editor for rows and columns
Fields that map directly to the component’s expected data structure
All data is stored in the page configuration, not in Salesforce records or CMS.
Display and preview
As soon as the data is entered, the component renders it immediately in Experience Builder, allowing you to:
Preview the result in real time
Adjust layout, formatting, or content directly on the page
When to use a Manual Data Source
The Manual Data Source is well-suited for the following Experience Cloud scenarios:
Static or page-specific content
Use the Manual when the content is tied to a specific page and does not need to be reused or updated dynamically across the site.
Small and simple data sets
For short lists, small tables, or limited datasets, manual entry is faster and easier than configuring a dynamic data source.
Demos and prototypes
Manual data is ideal for quickly building demo sites or prototypes without setting up Salesforce data models or CMS content.
Testing and layout validation
During development, manually controlling the data makes it easier to validate:
Component layout
Responsiveness
Sorting, filtering, or styling behavior
Full editorial control
When you need precise control over the displayed content and do not want it to change unless the page itself is edited, Manual is the safest option.
Example: Static product list on an Experience site
Imagine you’re building a public Experience Cloud page that showcases a small, fixed list of products with names, descriptions, and prices.
Add an Avonni Data Table or List component to the page
Select Manual as the Data Source
Enter each product as a row, with columns for name, description, and price
The component immediately displays the product list on the page
No Salesforce records or CMS configuration are required.
Tips
Prepare your data first: Organize values and labels before entering them to avoid rework.
Use clear field labels: This improves readability and maintenance in Experience Builder.
Always preview the page: Verify rendering, alignment, and behavior before publishing the site
Last updated
Was this helpful?