This page offers solutions for improving the speed of the Avonni Components package in Salesforce.
Last updated
Was this helpful?
This guide provides recommendations and considerations for optimizing the performance of Avonni Components when used within Salesforce Flows.
Avonni Components for Flows are designed to enhance your Flow screens and provide a rich user experience within the Flow Builder environment. While engineered for efficiency, their performance operates within the context of the Salesforce Flow runtime.
Several factors influence the speed and responsiveness of Avonni Components inside your Flows:
Flow Complexity: The overall design of your Flow significantly impacts performance. Flows with numerous elements, complex branching logic, multiple loops, or frequent data operations (Get/Create/Update Records) will naturally take longer to execute, affecting screen load times.
Salesforce Flow Runtime: Components run within Salesforce's Flow execution environment. Performance can be influenced by overall Salesforce org performance and current load.
Avonni Query Data Source (QDS) Advantage: For Avonni data components (like Data Table, List) used within a Flow screen, leveraging the can often provide more efficient data retrieval compared to using multiple standard Flow "Get Records" elements followed by assignments to populate the component.
Sandbox vs. Production: As with many Salesforce features, components may render, and Flows may execute slightly slower in Sandbox environments than Production orgs due to differences in resource allocation. Always perform final performance testing in Production or a Production-like Sandbox.
Minimize the number of elements on each screen.
Optimize loops and decision logic.
Perform data operations efficiently (e.g., update records in bulk after collection instead of inside a loop).
For components like Data Table or List within your Flow screens, use the integrated Avonni Query Data Source to fetch and filter data efficiently, reducing the need for multiple separate Flow data elements.
While building in any Sandbox is fine, conduct performance testing in an environment that closely mirrors Production.
These Salesforce settings can impact the performance of all Lightning Web Components, including Avonni's:
Caching: Initial load times for any LWC, including Avonni components (especially in the Flow Builder itself), might occasionally be longer due to Salesforce's internal caching mechanisms being populated. Subsequent loads are typically much faster.
Avonni Dynamic Components are specifically architected as native LWCs optimized for fast page loading, responsiveness, and native reactivity directly within the Lightning App Builder environment. If page load speed and direct page UI customization (like building custom related lists, dashboards, or unique record layouts) are your top priorities, Avonni Dynamic Components provide the superior, purpose-built solution.
Lightning Web Security (LWS): Salesforce generally recommends enabling Session Settings, which can improve the performance and security of LWCs.
While Avonni Components for Flows are excellent for enhancing Flow screens, if your primary goal is to build custom, high-performance UI elements directly onto your Salesforce App, Record, or Home Pages (outside of a specific Flow process), we strongly recommend using our separate package: .
Avonni continuously evaluates and enhances components for optimal performance. If you have specific performance questions or concerns regarding Avonni Components for Flows, please .