FAQs & Common Error Messages

Frequently Asked Questions

Can I copy components between orgs?

Yes - It's straightforward: Dynamic Components are stored as Custom Metadata records in Salesforce, making them highly portable between orgs using standard Salesforce deployment tools.

How It Works

Dynamic Components are stored as records in a Custom Metadata Type (CMDT) provided by the Avonni managed package. When you create a component like "Account Dashboard," it's saved as a single metadata record containing all the component's definition—layout, data sources, styling, interactions, and logic.

How many components can I create?

No hard limit: Create as many as needed, but consider maintenance overhead and organization.

Can Dynamic Components call Apex?

Yes: Components can invoke Apex methods through proper configuration and security settings.

Do Dynamic Components work offline?

No: Dynamic Components require server connection, like all Lightning components.

Can I version control my components?

Yes - Built-in version management: Dynamic Components includes a comprehensive version control system that allows you to maintain multiple versions of each component with safe experimentation and easy rollback capabilities

How do I migrate components from sandbox to production?

Straightforward process: Dynamic Components are stored as Custom Metadata records, making them easy to migrate using standard Salesforce deployment tools

Can I white-label Dynamic Components?

Yes: Full styling control allows complete customization to match branding.

What's the performance impact of Dynamic vs App Builder Components?

Similar: Both are Lightning components with comparable performance. Dynamic Components may be slightly slower if overly complex.

Can I use Dynamic Components on mobile?

Yes: Components work in Salesforce mobile app, but test thoroughly as mobile experience may differ.

How do I debug component logic?

Tools:

• Browser developer console (F12)

• Lightning Debug Mode

• Custom logging in component logic

• Salesforce debug logs for server-side operations

---

Common Error Messages and Solutions

"Unable to create component"

Cause: Metadata API permission or package issue

Solution: Verify "Modify Metadata Through Metadata API Functions" permission is enabled

"Component exceeds maximum size"

Cause: Component too complex or large

Solution: Break into smaller components or simplify structure

"Invalid field reference"

Cause: Referenced field doesn't exist or isn't accessible

Solution: Verify field API name and user permissions

"Event not found"

Cause: Event name mismatch in component communication

Solution: Ensure event names match exactly (case-sensitive)

"Unable to activate component"

Cause: Validation errors in component configuration

Solution: Review all error indicators in builder before activating

---

Still Need Help?

Can't resolve your issue?

• Email Support: [email protected]

• Report a Bug: See our Bug Reporting Guide

• Community Forum: Share experiences with other Dynamic Components users

Before contacting support:

1. Document exact error message

2. Note steps to reproduce

3. Include component configuration screenshots

4. Specify package version

5. Describe expected vs actual behavior

6. Test in multiple browsers

7. Try with different user permissions