Back
First attribute not entered, but new document creation success despite failing attribute is required
Has anyone else experienced the first attribute in a document being changed to "undefined" while creating a new document? Document creation does not result in an error, and it's just the first attribute that gets changed to "undefined" all others get passed along and is entered properly.
TL;DR
Developers are experiencing an issue where the first attribute in a document gets changed to "undefined" while creating a new document despite other attributes being entered correctly. Manually updating the attribute in the interface results in a "Server Error." One suggestion is to share an appwrite.json export of the collection for further assistance. Addendum: Manually updating (via appwrite web interface) said attribute in the document just spits out a "Server Error" message, so I can't even figure out what I should do (or try) to correct the first issue.
Creating a new document from the web interface does the same thing - all attributes entered correctly except the first one.
Nope, never seen that. Maybe you can share an appwrite.json export of your collection
