search
YouTube ChannelBook A DemoContact SupportJoin The Community

atomUnderstanding The Essentials

Six core concepts that unlock everything in Dynamic Components. Master these and you'll be able to build any interface — without writing a single line of code.

face-thinking

hashtag
Not sure if Dynamic Components is the right tool for your use case?

Read the Dynamic vs Flow Components comparison first — it takes 2 minutes and will save you from building in the wrong place.

hashtag
Suggested learning path

These five concepts build on each other — read them in order for the smoothest experience.

1

hashtag
Component Builder

Learn how to navigate the canvas, add components from the palette, and configure properties in the panel. This is the interface you'll use for everything.

🏗️ Component Builder →

2

hashtag
Target Page Object

Tells Avonni which Salesforce object your component lives on — Account, Opportunity, Case, etc. Set this before you try to use any record fields.

🎯 Target Page Object →

3

hashtag
Variables & Component Data

Variables are how data flows through your component. Use Salesforce field values, merge fields, or custom variables to drive text, images, and interactions dynamically.

⚡ Variables & Component Data →

4

hashtag
Component Visibility

Control when each component is shown or hidden — based on field values, user profiles, or record state. Build cleaner UIs by showing users only what's relevant.

👁️ Component Visibility →

5

hashtag
Publishing Your Dynamic Components

Once your component is ready, publish it and add it to a Lightning page in App Builder. Understand the difference between saving and publishing before going live.

🚀 Publishing Your Dynamic Components →

hashtag
All essential concepts

Cover

Component Builder

Navigate the canvas, add components from the palette, and configure properties. This is your main workspace.

After this: You'll know how to orient yourself and place your first component.

Cover

Target Page Object

Define which Salesforce object your component is on — this is what makes record fields like Account Name available.

After this: You'll understand why this step must come before connecting any data.

Cover

Variable & Component Data

Bind Salesforce field values to component properties to drive dynamic text, images, and conditions.

After this: You'll be able to make your UI react to real record data.

Cover

Component Visibility

Show or hide components based on field values, user profiles, or record state — for cleaner, context-aware UIs.

After this: You'll know how to write visibility rules for different users and scenarios.

hashtag
Publishing Your Dynamic Components

Once your component is built and configured, you need to publish it before it becomes available on Lightning pages. There's an important distinction between saving your work in the builder and publishing a version that users can see.

After publishing, you add your component to an App Builder page just like any standard Salesforce component — then save the Lightning page to make it live.

✅ After this, you'll know how to get your component in front of real users on any Lightning record or app page.

rocket-launchRead the Publishing guide →

Last updated

Was this helpful?