Over the past weeks, we introduced all kinds of new features in the import event. You can process imported records by a callback action to use them in subsequent events for example. However, we wanted to go even one step further. Because what if you want to assign values to the whole import file before every record has been validated? Therefore,
Peter Arentsen
Recent Posts
We improved the performance of sorting form components and grid filters in the back office module of your application. Thanks to several changes, we made the sorting as fast as you can drag and drop in this area. You don’t have to wait anymore before your change is saved. After you have dropped the component that you were sorting, you can start
It is now possible to pass your imported records to the callback actions for import events. This new piece of flexibility should be enough to cover all your import-ant needs *wink*
You'll find the callback action option at the bottom of an import event
This feature enables you to use the imported records in subsequent events.
Think of
How often do you need pagination for your Betty web pages? This will often lead to slow page loads. To help you build pages that load a lot quicker, we've introduced the count_full_collection() expression function.
Currently, if you want to paginate over a certain collection, you have to fetch the collection twice. Once with the limit and
We updated the actions part of the platform with an improved loading time of actions and action events in the builder mode. Please don't mistake this with execution time of actions. This improvement could be done by reducing some side effects that previously occurred by opening actions and events. Large applications (with many actions and events)
