Last updated
Was this helpful?
Here are the most common errors when adding a flow with Avonni components inside.
If you're running into issues with Avonni Components, ensure the flow you're having issues with is running on the latest API version. You can check this in your flow settings. This might help resolve some problems up front.
You'll see this error message on a flow in Experience Cloud if the user doesn't have permission to run it. Ensure that users with the selected profile either have general flow permissions or that their profile is listed explicitly as able to access this flow.
This error happens when either:
The affected user doesn't have the necessary permission set assigned to them.
The selected user doesn't have a license assigned to them.
To fix this, you can add a license to the user by going to the Installed Packages page in Salesforce Setup and then clicking Manage Licenses.
If you see the flow and Avonni Components on your page, but the components are empty (no data is displayed), it's usually a permissions issue.
Check these two things:
Object and Field Permissions: Ensure the users experiencing the issue have at least "Read" access to the object and fields you're trying to display in the Avonni Components.
Apex Class Access: Check the affected user's profile to ensure they have access to the necessary Avonni Apex classes. If not:
Go to the profile settings.
Search for "Avonni Components (avcmpbuilder)" APEX classes.
Add those classes to the profile
You might encounter problems deploying flows built with Avonni Components from your sandbox to production. This can result in various error messages. In most cases, these errors happen because different versions of the Avonni package are installed in your sandbox and production environments.
To fix this, ensure you're running the same version of the Avonni package in both your sandbox and production. You can always update to the latest version from our .
