Quickstart Guide
Get started with AX App Builder Components in minutes. This guide walks you through building your first component using a practical example.
What You'll Build
A Data Table on an Account record page that displays related Opportunities with filtering, inline editing, and search. This example covers the core setup patterns you'll use across all AX components in Lightning App Builder.
Prerequisites
Avonni package installed in your Salesforce org
Lightning App Builder access
Permission to edit Lightning pages
Step-by-Step Setup
Configure the Data Source
These settings tell the component what data to display:
Object API Name
OpportunityThis tells the component to pull data from the Opportunity object.

Filter
AccountId = '{{Record.Id}}'This dynamic filter shows only Opportunities related to the current Account. The {{Record.Id}} syntax automatically references the current Account's ID.
Important
Notice the single quotes around the dynamic reference. This follows SOQL syntax rules where text and ID values must be enclosed in single quotes. The filter essentially becomes a SOQL WHERE clause, so it must follow proper SOQL formatting.

Column Field Names
Name,StageName,Amount,CloseDateThis comma-separated list defines which fields appear as columns in your table, in the order specified.

Order By
CloseDate DESCThis sorts Opportunities by Close Date, showing the most recent first.

Enable Editing and Filtering
Editable Fields
StageName,CloseDateUsers can edit these fields directly in the table without navigating away.

Filterable Fields
StageName,OwnerIdThis creates filter controls above the table for these specific fields.

Search Options
Toggle Allow Search on All Columns to On
This enables keyword search across all visible columns
What You've Created
Your Data Table now provides:
Dynamic Data: Automatically shows Opportunities for the current Account
Interactive Editing: Users can update Stage and Close Date without leaving the page
Powerful Filtering: Built-in filters for Stage and Owner
Search Capability: Find specific Opportunities by keyword
Professional Appearance: Clean, card-based layout with clear headers
Performance: Pagination prevents slow loading with large datasets
Understanding the Key Concepts
Dynamic Record References
The filter AccountId = '{{Record.Id}}' demonstrates how components automatically adapt to different records. When users view Account A, they see Opportunities for Account A. When they view Account B, they see Opportunities for Account B.
SOQL-Style Configuration
The field specifications like Name,StageName,Amount,CloseDate mirror how you'd write a SOQL SELECT statement. This approach gives you precise control over data display while staying familiar to Salesforce developers.
Field-Level Security
Your component automatically respects Salesforce permissions. If a user can't see the Amount field in standard Salesforce, they won't see it in your Data Table either.
Expanding Your Component
Now that you have a working Data Table, try these enhancements:
Add More Filters
Include Additional Fields
Refine Your Filter Logic
This shows only open Opportunities.
Enable More Editing
Next Steps: Try Other Components
Apply these same concepts to other Avonni components:
Kanban Board for Visual Pipeline Management
Object: Opportunity
Filter:
AccountId = '{{Record.Id}}' AND IsClosed = falseGroup Field: StageName
Title Field: Name
Summary Field: Amount
Calendar for Activity Tracking
Object: Event
Filter:
WhatId = '{{Record.Id}}'Title Field: Subject
From Field: StartDateTime
To Field: EndDateTime
Metric for Key Performance Indicators
Object: Opportunity
Filter:
AccountId = '{{Record.Id}}' AND StageName = 'Closed Won'Field: Amount
Aggregate Function: SUM
Label: Total Closed Revenue
Troubleshooting Common Issues
Best Practices Learned
From this exercise, you've learned the essential patterns used across all Avonni components:
Start with the data source (Object API Name)
Filter to relevant records using SOQL WHERE syntax
Specify fields in comma-separated format
Use dynamic references with
{{Record.FieldName}}syntaxConfigure headers for user context
Test with real data to verify functionality
These same principles apply whether you're building a Gallery of product images, a Map of customer locations, or a Timeline of case activities. Master this Data Table example, and you'll be ready to implement any Avonni component effectively.
Last updated
Was this helpful?

