What's New
Version 1.29: Direct Links Access
Enhancements
➤ Automatic Record Refresh After Flow Execution Now, when a flow runs from a Dynamic Component and updates a record, the page record will automatically re-query and display the updated data. This eliminates the need for manual refreshes and applies seamlessly to records updated via the "Execute Flow on Load" interaction, requiring no additional configuration.
➤ Auto-Fill Folder Field When Creating a Component Inside a Folder When creating a new component from within a specific folder, the Folder field is now automatically prefilled with that folder’s name. This slight but time-saving improvement eliminates the need to reselect the folder you’re already working in manually.
➤ Direct Component Documentation Access Now, every component includes a direct link to its corresponding documentation page. Simply look for a "question mark" icon within the component to instantly navigate to its dedicated help content. This makes it much easier to find the information you need, right when you need it!.
Bug Fixes
➤ Unable to Save 0 as Default Value for Number Variables
Previously, when setting the default value of a number variable to 0, it wouldn’t save properly. Using 1 worked, but 0 was ignored. This has now been fixed—0 is saved as expected.
➤ Avonni Metric: Main Value Should Be a Number The principal value in the Metric component was incorrectly treated as a text field, while the secondary value was numeric. We've corrected this so the main value is now typed adequately as a number, in line with the component’s purpose.
➤ Missing Operator for Decimal Fields in Visibility Conditions When applying visibility conditions to number fields with decimal values, the operator dropdown wasn’t showing. This issue has been resolved, and you can now configure conditions for decimal fields as expected.
➤ Avonni List: Reordering Error (orderFieldName Cannot Be Null)
If you enabled sorting and used the reorder interaction in the Avonni List component, an error would occur when trying to reorder items:
“Error Updating Records Order. The orderFieldName cannot be null or empty.”
We’ve fixed this by ensuring that orderFieldName is now correctly handled.
➤ Avonni Data LWC Container: Can’t Select Rich Text or Long Text Fields Rich Text and Long Text Area fields were missing from the field mapping options in the Data LWC Container. They’re now selectable and fully supported.
➤ Preview Issues with Dynamic Components in Builder In some cases—depending on metadata structure—it wasn’t possible to preview or exit preview mode for a dynamic component inside the App Builder. This has been addressed to ensure smoother preview transitions.
➤ Avonni Kanban: Custom Column Order Not Applied Custom column ordering in the Kanban component wasn’t functioning as intended. We’ve now aligned its behavior.
➤ Data Table Export Now Respects User Locale for Date Formats
Previously, when exporting data from the Data Table component, date fields were consistently formatted in the US style (MM/DD/YYYY), regardless of the user's locale settings in Salesforce. With this improvement, exported dates now follow the correct regional format—such as DD/MM/YYYY for many European locales—ensuring consistency with how dates are displayed in the Salesforce UI.
➤ Slider Component Freezes When Switching from Decimal to Percent Switching the unit from Decimal to Percent in the Slider component previously caused the preview to freeze, making the component unresponsive. This issue has been fixed—unit changes now apply smoothly without disrupting the preview experience.
Last updated
Was this helpful?