🐛 Bug: On locking view, form field order is not retained.
Please confirm that the bug report does not already exist
- [x] I confirm there is no existing issue for this bug.
Steps to reproduce
After setting field order via drag-and-drop in the form builder and locking the view, the order appears correct for the editor. However, in the public (anonymous) view — even in incognito — the order is different. The same form has different field orders depending on whether you’re: • Logged in as editor • Viewing it as an anonymous user In some cases, layout corruption increases over time (forms “break” further the next day). Re-locking and reordering helps temporarily, but the issue reappears even after full layout reset.
Desired Behavior
The form field order should persist once saved. Locked views should guarantee consistent layout across all users and roles. Anonymous/public views should render exactly as built by the form editor.
Project Details
Node: v22.15.1 Arch: x64 Platform: linux Docker: true RootDB: mysql2 PackageVersion: 0.263.4
Attachments
No response
Can u expand on what do you mean by layout corruption.
Between locking and changing order have you added new fields to the table ?
@o1lab No, no new fields were added between locking and noticing the issue. By “layout corruption” we mean: after locking, the form fields appeared in the correct order, but next day the order changed on its own. The editor view kept the correct order, but the public view did not.
@ilyak0 we tried few variations- but are unable to reproduce this issue. can you share a screenshot or video recording for reference?
Or send us your form to support at nocodb dot com too.
@dstala Sure, pls see the video. https://drive.google.com/file/d/1BZDQHXzvCDJpTxaRb1BECeG4r3ZqylTr/view?usp=sharing
Unfortunately, there is no audio track recorded, but it should be mostly self-explanatory.
I open a public view from the edit view to make sure it’s the same form. First items do correspond each other, but starting from "отчество мамы" there is a discrepancy. I scroll down most of the form content so you may check that there are many counts of such discrepancies, unfortunately.
Any updates on this issue please? May be in conjunction with the other issue I've raised which is reproducible? https://github.com/nocodb/nocodb/issues/11550
Hey, we need a clear way to reproduce this issue. We have tried all possible variations and dont see an issue.
@ilyak0 please reopen this ticket if issue still persists in v264.6. Unfortunately, we were unable to reproduce this issue previously. Let us know if you still continue to see this.