Problems with the button on the query page

Setup:
{“version”:“5.1.9”,“edition”:“enterprise edition”}

Hello everyone!
I have a button column in my table that opens the columns single page in the universal app. For that I have added an additional column which stores the row ID. The button then pulls the row ID out of that column like so: https://seatable.XYZ.com/external-apps/1223456789/page_id=ABCDE&record_id={Row ID}
This works perfectly fine when using the buttons in the normal base view.

The Idea behind that is that a user of the universal app Query’s for entries via the query page type and then can open the single page view by just clicking the button.

The problem: When using the buttons inside the query page of the universal app, the button always opens the single page type of the first entry of the database instead of the one of the row I just clicked on.

Is this a SeaTable side bug, or is there any way for me to fix this? Maybe a workaround?

I confirm the observed functional restriction when you refer to the row ID in a formula column. (In SeaTable 5.1, a button on a query page cannot access content in formula columns.)

There are two workarounds:
1.) Copy the row ID in a text column (the button can access the content in text columns)
2.) Use a table page rather than a query page

Good news: This function restriction will be mended in SeaTable 5.2. In version 5.2, buttons on query pages can access formula data.

1 Like

thank you for the heads up! looking forward to 5.2 :slight_smile:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.