Is it possible to downgrade from 2.1.0 to 2.0.6?

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 2.1.0

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

Docker image: baserow/baserow:2.1.0

What are the exact steps to reproduce this issue?

After updating from 2.0.6 (I think? Maybe it was 2.0.1) to 2.1.0, my application stopped working. The “create row” action throws an error if a field is empty, and I have lots of optional fields…

So, until I can research more and help find the bug/regression, I’d like to downgrade to 2.0.6.

I attempted to change the tag already, to image: baserow/baserow:2.0.6, but it fails to start.

Can you post the error you get when trying to create a new row and the error you get when starting baserow?

1 Like

The error I was getting during startup after rolling back to 2.0.6 had to do with Redis. I renamed the file inside the Redis folder so that it would get recreated, and the rollback worked after that.

While I was running 2.1.0, I was seeing errors regarding adding a new row (using a button in an application) because a field was empty (I have lots of optional fields, so empty fields are normal for me).

I also got errors about updating a row, because in my application there’s a single button that performs lots of actions (including updating rows), but like I said everything is optional so if there’s an empty input box it would say something like “Row ID required” (although I’ll have to go back and test again when I have time).

This was a problem in previous versions, but it was fixed at some point, maybe 2.0.1.

1 Like

Could you send us a screenshot of how the actions are configured?

Ideally if you could send us (privately) the export of the application (without data) it would be great.