How to update a row in Baserow App Builder using a condition instead of Row ID

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

version 1.34.2

If you are self-hosting, which installation method do you use to run Baserow?

I am using Docker.

What are the exact steps to reproduce this issue?

In the Application Builder’s “Event” (e.g., when the Submit button is clicked), how can I perform an “Update row” action not by specifying the Row ID directly, but by updating the row that matches a specific condition — for example, a row where the “Date” field is equal to 2025-07-07?

Hi @hslee, this functionality is covered by this GitLab issue: Add support for advanced formulas (#3164) · Issues · Baserow / baserow · GitLab which is on the roadmap for the next release (but is subject to change)

It might not be applicable but I figured out a way to get around this, at least for a specific use case.

I was trying to basically create a “bookmark” button to save a row to a user. I had to create a bridge table, with links to the user and the thing they were bookmarking. I used a formula to combine the user ID and the linked row ID into a unique number. In the page data source used the “search” option to look for the parameter ID+User ID (which was the unique row of their bookmark). Essentially it would return either an empty row (which was a placeholder row) or the bookmark that was previously made; if there was a bookmark, it could delete it; if not, it would create one.

It sounds like it’s a different situation but just wanted to share if something like that might work for you.

Thank you for the update and for pointing me to the GitLab issue.

I’ll keep an eye on the roadmap and look forward to that feature being released.
Much appreciated!

Thank you very much for your helpful response. I really appreciate it.

I’ll give it a try by creating a bridge table, as you recommended.
If it works, I’ll make sure to share the outcome here.

Thanks again!

p.s. : I attempted to delete my earlier comment to post a revised version, but it didn’t fully disappear, so things may look a little confusing. Thanks for your understanding!