Avonni Components Community

Hello Domini,

Thank you for reaching out. A good first step to resolve this is to ensure you’re running the latest version of the Avonni Package. You can find direct links here: https://docs.avonnicomponents.com/changelog

If the issue continues after updating, please reach out to us at support@avonni.app or through our live chat on the documentation site: https://docs.avonnicomponents.com/

Thanks,

Hi @Kevin Pathiakis, 

This usually happens because the trend direction is based on how the metric is interpreted, not just the value change. 

Check: 

•  Whether your metric is set to “Higher is better” vs “Lower is better”
•  The comparison logic (current vs previous)
•  If your secondary value is being treated as a baseline or delta

If “lower is better” (e.g., cost, errors), a decrease may show as positive (green). 

Adjust the metric settings accordingly to match your use case. 

If you find this helpful feel free to mark it as Best Answer !!!! 😊 

Thanks and Regards. 

Hi Janardhana

Thanks for sharing this

What you’re describing does sound like unexpected behaviour, and potentially a bug.

I just wanted to check if you’re still experiencing this issue. If so, could you reach out to us at

so we can take a closer look and troubleshoot with you directly? 

If you’re able to include details like your component configuration, and screenshots, that would help us investigate. 

Thank you, 

 Sarah

Hi Janardhana

Apologies for the delayed reply here, we somehow missed this message. 

At the moment, this isn’t something that can be customized. The empty state illustration follows a standard Salesforce pattern, which our components currently adheres to. 

That said, we understand the need for more control over the appearance. 

Please reach out to us at support@avonni.app

so we can log it as a feature request and consider adding it to our roadmap. 

Thank you, 

 Sarah

This is a great question, Jack! To clarify, the new package is not a replacement for your current Flow components; instead, it’s a complementary solution

designed for different parts of Salesforce. 

Think of it as having two different toolsets for two different jobs: 

1. The 70+ Flow Components Package (What you have now)

• Where to use it: Exclusively inside the Salesforce Flow Builder.
• Best for: Guided, multi-step processes and wizards that require moving a user from Screen A to Screen B.

2. The 40+ App Builder & Experience Components Package

• Where to use it: Inside the Lightning App Builder (Record Pages) and Experience Builder (Sites).
• Best for: Enhancing your actual page layouts or building customer portals. These components live directly on the page and don't need to be wrapped in a Flow to work. Use this when you want to add high-performance, reactive components (like timelines or data tables) directly onto an Account page or a public site.

Is there an "Upgrade" process? No upgrade or migration is necessary. Because they serve different purposes, both packages can (and often should) coexist in the same org.

Your existing Flows will continue to work exactly as they do now. 

When to use one versus the other?

• Use Flow Components when building a process-driven "wizard."
• Use Dynamic Components to enhance a Record Page or build an Experience Cloud site.

The real power comes when you use both together. For example, you can build a Dynamic Component for a Record Page to display data beautifully, and from that component, launch a Screen Flow

(via a dialog or panel) to handle complex user interactions. 

This creates a powerful extension of the no-code solution builder in Salesforce—giving you total flexibility over both the page layout and the business logic.

I hope this helps clear up the path forward!

Great suggestion @Eric Burté. Based on Eric's suggestion, @Lewis Blau building on Eric’s idea: in the Avonni Data Table, add your formula field as a column and set its type to Rich Text. That way, the formula’s image output will render in the table 

Hope this helps.