Avonni Components Community

Hi Juan Carlos,

Thanks for raising it here. There was no formal announcement. The public repositories had not been maintained for about two years and few teams still relied on them. As Salesforce kept evolving, keeping them up to date became unrealistic, so we brought everything together in one place: the Avonni LWC Components package on AppExchange. It includes many more components, and it is where we ensure every Salesforce release is properly supported.

Your fork is yours: the code keeps working and you are free to keep evolving it on your side.

The documentation moved to https://docs.avonnicomponents.com/lwc-components (the old avonnicomponents.com address redirects there), with attributes, events and code examples for each component. It documents the current package, so some details may differ from the version in your fork.

If you'd like to see what the package adds compared to the original components, send me a message and I'll give you a quick tour.

Cédric

Hello Sue, 

Yes, I've logged a request to add the no-results settings to the AX - List and AX - Data Table: your own message, and options to hide the image or the text. Those settings already exist on our other components, so it's a matter of bringing them over. I can't give a date yet.

The image itself can't be swapped for another one, and it already renders at its smallest size, so the request covers hiding it. 

Best,

Hello Brad, and thank you for the kind words! 🙌 

Great question. The Metric component doesn't have a built-in link property today, and the value itself isn't clickable, so you can't wire the number directly to a report. 

But you can get that click-through behavior with a small tweak: drop a Button or Button Icon next to the metric, something like "View report," and wire its click to the Navigate interaction. Navigate can take the user to:

• A web page: paste the report URL and choose whether it opens in the same tab or a new one.
• The report as a record: set the page type to Record Page, object Report, and pass the report Id to open it natively in Lightning.

Either way, you get the "click to my report" experience with the KPI and the action in the same card. If your metric is query-driven off a record, Navigate also supports {{Record.FieldName}} tokens so the destination can be dynamic. 

I've submitted a feature request to make the metric value itself clickable. In the meantime, the button approach should get you what you're after. 

Let me know if you hit any snags setting it up!

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