For the complete documentation index, see llms.txt. This page is also available as Markdown.

AX - Dynamic Component

Overview

AX - Dynamic Component is a Lightning App Builder component that lets you embed advanced components from Avonni's Dynamic Components platform directly onto your record pages, app pages, and home pages.

Use it when you need capabilities beyond standard App Builder components—like advanced styling, conditional logic, nested layouts, or access to 70+ specialized reactive components. Build your component in the Dynamic Components app, then drop it into App Builder using this connector.

Perfect for creating sophisticated custom interfaces, dashboards with complex interactions, or branded experiences that require more control than standard components offer

Getting Started

Use this simple tutorial to learn the basics of the Dynamic component and start building your use cases.

spinner

When to Use Dynamic Components

Choose Dynamic Components over standard App Builder components when you need:

Complete Component Library Access: Dynamic Components offers 75+ components, compared to ~15 in App Builder Components, including specialized widgets not available elsewhere.

Advanced Styling & Branding: Full visual control with custom styling options, branding elements, and design flexibility beyond Lightning App Builder's constraints.

Complex Interactions & Logic: Components that communicate with each other, conditional behaviors, and sophisticated user interactions that aren't possible with basic configuration.

Component Composition: Ability to combine multiple components into integrated layouts and embed components within other components.

Specialized Use Cases: Access to advanced components designed for specific business requirements that aren't covered by the standard App Builder selection.

Check the Dynamic Components Documentation Center


Prerequisites

Before using the Dynamic Component, you must:

  1. Have Dynamic Components Access: Ensure you have access to Avonni's Dynamic Components platform

  2. Create Dynamic Components: Build and configure your desired components using the Dynamic Components builder

  3. Activate Components: Activate your Dynamic Components to make them available for selection

  4. Proper Permissions: Ensure users have appropriate permission sets for both App Builder and Dynamic Components


Configuration

Property
Type
Required
Description
Example

Component Name

Dropdown

Yes

Select the pre-built Dynamic Component to embed on this Lightning page. Only activated Dynamic Components appear in this list.

Advanced Sales Dashboard<br>Interactive Product Catalog<br>Custom Metrics Widget

Display as Card

Checkbox

No

Wraps the Dynamic Component in a styled card container for better visual presentation and separation

Checked for dashboard sections


Key Considerations

  • Component Design: Give components clear, descriptive names, test them in the Dynamic Components builder first, and design responsive layouts that fit Lightning page constraints.

  • Integration Strategy: Use Dynamic Components for functionality beyond standard App Builder components, and combine them with standard components and card containers as needed.

  • Performance: Monitor page load when embedding complex components and test across different user profiles and permission levels.

  • User Experience: Provide context through surrounding page elements, test with real end users, and document any special interactions for training.


Troubleshooting Common Issues

  • Component Not Available in Dropdown: Confirm the Dynamic Component is activated and that you have permission to access it.

  • Component Not Displaying Correctly: Verify it works in the Dynamic Components builder, check the browser console for conflicts, and ensure the layout has adequate space.

  • Functionality Issues: Test the component independently, confirm its data sources are configured, and check user permissions on the underlying data.

  • Performance Problems: Compare page load before and after adding the component, simplify or split complex components, and test with realistic data volumes.

Last updated

Was this helpful?