Problem with open row of table in another page

1

Hi, i have a problem as superhuman may have change something in there system.
I used to be able to open row from table in another page while staying in the current page. but now with new system, everytime i open row in another page, it will jump to that table page.

For example,

I have a table for the database name “db_wo” and have another button to add new row in another table called “form_wo” to fill in the data before submit it to “db_wo”

usually when i press the button add new row, it will open a view from “Form_wo” for the user to fill the information while still staying in the same page he is on.

However, with some change in the system, right now when i press the button, it would automatically jump to the page where the table “Form_wo” is , instead of just open the row in the same page.

Is there anything to fix this, because my whole system is now ruined because of this

1786420058434
17864200584341571×905 200 KB

2

I’ve run into exactly the same issue. The behavior of the OpenRow() formula used to be different. Has something changed? If this is the new intended behavior, we’ll have to change the entire logic :thinking:

The most important thing is to understand whether this is the new permanent behavior or just a temporary bug. Right now, this issue is preventing people on our team from working properly, and if this behavior is here to stay, we’ll have to change the entire logic.

3

This MUST be considered as a serious BUG.

So many of our workflows over the years depend on the previous behavior.

To change that, BREAKS the workflow logic.

4

Yeah, this pretty much renders most docs dead. Anyone from Coda care to chime in?

5

Hey all,

Update here: the team is aware of the bug, and a fix is in progress as we speak. We expect this to be resolved by this afternoon and I will update this thread once it is.

6

Thanks for resolving this

7

thanks, it’s back to work