I am using SeaTable Cloud and have created a Universal App with a Single Record page.
On this page, I have two buttons. Both buttons perform essentially the same process, but on different fields:
- Check a checkbox field.
- Record the execution date in a date field.
- Send an email.
The only difference between the two buttons is the fields they modify and the content of the email.
The first button I added at the beginning of the page construction, works correctly.
The second button, which I added somewhat later during the construction of the page, does not work and displays the following error when clicked:
“Permission error. Please refresh the page.”
Refreshing the page does not resolve the issue.
Tests performed
I performed several tests to isolate the problem:
- The user testing the application is an administrator.
- The relevant rows can be modified by everyone.
- I tested the issue in Chrome as well as my original browser. The behavior is identical.
- I created a new checkbox field specifically for testing.
- I created a new, very simple button whose only action is to check this new checkbox.
- This simple button still produces the same permission error when used on the problematic Single Record page.
- I created a Table page in the same Universal App, using the same table and the same button.
→ The button works correctly on the Table page. - I created a new Single Record page, using the same table and the same button.
→ The button works correctly on the new Single Record page. - I also tested the problematic button with only the checkbox modification, removing the other actions.
→ It still produces the permission error on the original Single Record page. - The first button, which was created earlier during the construction of the page, continues to work correctly on the original page.
Current conclusion
The problem therefore appears to be specific to the original Single Record page, rather than to the button, the fields, the user’s permissions, or the browser.
The same button works:
- directly in the Base;
- on a Universal App Table page;
- on a newly created Universal App Single Record page.
However, it fails on the original Single Record page.
There also seems to be a possible relationship with the order in which the buttons were added to the original page: the first button added works, while the second button added later does not.
Any idea where the problem could be ?
