Function gives unauthorized error when writing relational attribute; it works when I comment it out
- 0
- Tools
- Databases
- Web
I am on free tier.
I have function that has three attributes:
- A stand alone attribute (required)
- A many to one relationship attribute
- A many to many relationship attribute
When I run createDocument(), I get the error about user not having the permission to perform that action. However, when I comment out the relationship attributes, and only fill out the stand alone attribute, the createDocument() function runs smoothly. I do not understand why. I am more confused because the relationship attributes in their respective collections get created. It is only in this particular function that gives the unauthorized error. I am very confused.
export const makePost = async (name, linksData, comment) => {
console.log({ name, linksData, comment });
try {
const user = await createUser(name);
// User gets created successfully
const links = await Promise.all(
linksData.map(link =>
createLink(link.href, link.companyName, link.item)
)
);
// Links get created successfully
// gives error when user and link are not commented out,
// runs smoothly when user and link are commented out
const res = await databases.createDocument(
dbEnv,
postsCollEnv,
ID.unique(),
{
user, // Many to one relationship
links, // Many to many relationship
comment // Required attribute
}
);
console.log('Post created successfully:', res);
return res ? res : null;
} catch (error) {
console.error('Error creating post:', error);
return null;
}
}
Recommended threads
- Function permissions
In my app I have a CreateUser flow which makes several documents and at the end uses the functions.createExecution() to call a server-side function to create a ...
- Google Auth not working in a React App
Authentication with Google has failed. It redirects back to the signin route in React. Attached screenshots for configuration of Google console and Appwrite Go...
- Bug Report: Crash when trying to createR...
https://github.com/appwrite/sdk-for-android/issues/96 I think the bug is related with this one https://discord.com/channels/564160730845151244/1443887021314539...