Previously, attachment columns on tables always allowed users to upload multiple attachments. Today, we've updated the attachment column to give the option to allow users to limit them to a single attachment. Uploading a new document to a single attachment column will override any existing content.

Centralize your JavaScript management in Budibase. Create and edit JavaScript snippets in one place, and reuse them anywhere in your application. This update simplifies updates and ensures consistency across your project. Access via the </> icon above any JavaScript in Budibase to access your code snippets.

Read the launch blog to learn more.

With the Forms template, you can now select one of three form types when selecting your screen in the design tab.

  • Create a new row: For capturing & storing new data from your users
  • Update an existing row: For viewing & updating existing data
  • View an existing row: For a read-only view of your data

For more information, please read the launch blog.

In the latest 2.21.0 release, we've introduced significant improvements to SQL query aliasing. This enhancement simplifies the complexity and reduces the size of the SQL queries generated for databases when using DS+. A critical fix included in this release addresses the limitation with SQL tables having long names, which previously led to exceeding character limits in SQL queries.

We have also introduced a new environment variable, SQL_LOGGING_ENABLE, for self-hosted users. This addition allows users to view the SQL queries Budibase is executing on their SQL databases.

We've introduced a new feature that allows users to customize the delimiter (separator) used in CSV file exports. Previously, the default delimiter was set to a comma ',' which remains the default setting. However, users now have the flexibility to choose from a preset list of delimiter options to suit their data formatting needs.

Please note, this configuration is exclusive to CSV file exports and does not apply to JSON file exports.

Budibase now supports the automatic generation of nested schemas for REST queries that return arrays of objects. This functionality facilitates the display of related nested data in various formats, including tables. This feature is also designed for use with databases that utilize nested documents, such as MongoDB, Firestore, Elasticsearch, and DynamoDB.

A key improvement is the reduction in required network calls for nested data display. Instead of the previous two-query approach (one for top-level data, another for nested data), a single query now suffices, boosting application performance.

This functionality requires the creation of new queries for schema generation to apply. Existing queries will remain unaffected, preserving their current behavior.

Release Highlights:

  • Leverage n8n's extensive library of 775 nodes to unlock a range of powerful automated workflows directly within Budibase.
  • Streamline your data administration by managing Budibase-stored data seamlessly through n8n.

Read the launch blog to learn more about this release.

As of version 2.19.2, we've enhanced the functionality of the "Selected Rows Binding" for tables with "Allow row selection" enabled. This update provides users with an array of selected row data directly accessible through the bindings drawer beneath your table. This enhancement enables more versatile manipulations such as:

  • Deleting Selected Rows: Easily remove selected rows from your table.
  • Displaying Selected Row IDs: Utilize the pluck helper to display selected row IDs, enhancing readability.
  • Calculating Sum Totals: Combine pluck with sum to calculate totals (e.g., total weight) of selected rows, with toFixed ensuring precision.

Deprecation Notice: Selected Row IDs
Please note, the previous version of selected rows binding, which provided only Row _ids, is deprecated as of this release. While it remains available for backward compatibility, it will be phased out in future versions. We encourage all users to transition to the new binding method to take full advantage of the improved functionality.

For detailed instructions on how to utilize these new features and prepare for the deprecation, please refer to our documentation.

You can now make your app logo into a clickable hyperlink. This enhancement is particularly useful for setting your logo as a quick and convenient link back to the home screen or any other pivotal area of your application.

For guidance on how to implement this feature, refer to the Navigation section in our documentation.