Single record entire page vanished

User Talk Apps
1

This problem occured on Seatable Cloud.

I’ve encountered bugs twice in the last few days while building pages in a universal app, specifically with “single record” type pages.

The first time, the content of the single record page I had laid out vanished completely after I visited another page in my app. I rebuilt it from scratch, and it seemed to work.

This morning, I was building a new single record page for a different table; I checked another page to verify settings and ensure a similar layout, and the page I viewed glitched out. As you can see in the image below, nothing is displaying on the page (it’s the same issue as the first disappearance, so the page had actually been finished). It’s not even showing the correct title —it displays the title of the second page I was currently building. So now I have to rebuild that page entirely all over again. Is there any chance I can recover it if I didn’t create a snapshot?

image
image1862×499 14.3 KB

I really need to get into the habit of backing up my apps more often.

2

Thanks for reporting the issue. We will check it soon.

3

This bug occurred again this morning.
While working on building my app, I recreated the single-record page that had previously disappeared. After making a few changes, I discovered that another single-record page had suffered the exact same bug: all the information it contained was no longer visible and appeared to have been partially replaced by data from the page I was currently building (this is confirmed by the title, as the page was displaying a title that didn’t belong to it).

image
image1236×821 20.2 KB

All three pages are available if you would like to access and take a look at them.

My explanation might not be entirely clear, so to summarize and link it to the screenshots:

  1. Building the “Suivi cotisation 2027” page: everything was OK
  2. Building the “Suivi commission” page
  3. First bug: content of the “Suivi commission” page disappeared and was partially replaced by “Suivi cotisation 2027”
  4. Rebuilding a new “Suivi Commission(test)” page
  5. Second bug: content of the “Suivi cotisation 2027” page disappeared and was partially replaced by “Suivi Commission(test)”
4

Hi,

I would like to know if you have managed to identify the problem and if a fix is ​​planned soon ?

I am waiting for this improvement so I can avoid recreating pages that end up disappearing.

Thanks for any update you could give me.

5

I don’t know if this help.

I found a related thread on this forum that might explain what’s happening: “New pages in App disappeared” (SeaTable Dedicated 6.0.10). The explanation given there is a concurrent-editing race condition in the App Builder:

  • User A opens the app in edit mode
  • User B also opens the app in edit mode
  • User B makes several changes (saved)
  • User A makes one edit based on their older version of the app (also saved)
  • Because User A is working from an outdated version, User B’s edits get overwritten

This matches what’s described here: a newly built single-record page “overwrites” or mixes with another existing page’s content/title, likely because two edit sessions (same user in two tabs, or two different users) were saving structural changes to the app’s page list at overlapping times.

That thread mentions that in newer versions the page navigation structure is managed server-side to help with this, but it doesn’t appear to be fully solved yet.

As a workaround until this is fixed: avoid having the App Builder open in edit mode in more than one tab/session for the same app at the same time, and take a snapshot before making significant changes to single-record pages.

6

We have found the cause for this issue. The fix should be included in the next version 7.0.

7

Great, thanks for the update :+1:

That’s true; I did have two tabs of the same app open when the bug occurred. I’ll be careful about that when making future changes to the app.

Many thanks for your replies.

Edit : the bug just happened again while I only had a single tab of the app open. I’m therefore going to wait for the new version before proceeding further with the app’s development.