Server-Side function: Creation of 2 different documents in 2 different collection Weirdness
- 0
- Databases
- Functions
Hello all, I was wondering if anyone had some insight into this!
I have a server-side function that will sign up the user and after signing them up creates 2 documents in 2 different collections (within the same DB) Making one document works just fine! Once I add in making the second document (same DB different collection) to my function, it breaks it in a weird way. Signs up user ✅ creates 2 documents ✅
the 2 documents that are supposed to be in 2 different collections end up only going to the first collection and it breaks the documents (No data in either of them), It worked perfectly with creation of one document, but once you add the second document in a different collection it breaks.
any insights into what may be going on, or if im messing up somewhere along the way?
Would it be better to have a secondary function for the 2nd collection/document that triggers within my first function? or upon the execution of the original function?
Doc IDs replaced (they both have unique IDs (doubt the doc ids are sensetive information but just incase)) This is the view (minus the doc IDs) but the documents show up as completely empty other than an ID
^ For the above realized I was just making a rookie mistake! Figured this out!
Recommended threads
- Type Mismatch in AppwriteException
There is a discrepancy in the TypeScript type definitions for AppwriteException. The response property is defined as a string in the type definitions, but in pr...
- What Query's are valid for GetDocument?
Documentation shows that Queries are valid here, but doesn't explain which queries are valid. At first I presumed this to be a bug, but before creating a githu...
- HTTP POST to function returning "No Appw...
Hi everyone, I’m running into an issue with my self-hosted Appwrite instance. I’ve set up my environment variables (APPWRITE_FUNCTION_PROJECT_ID, APPWRITE_FUNC...