Optimizing Member Updates in Teams Collection | Payload | Page 1

somber sandBOT Mar 2, 2025, 5:10 AM

#

Let's say I have a teams collection that has a field called members which is a relationship field to users. As far as I understand it I can add new members like this

await payload.update({
  collection: 'teams',
  id: teamId,
  data: {
    members: [...existingMembers, newUserId],
  },
});

is there a better way? Do I need to fetch existing members whenever I need to add to or remove from members ?

lapis summitBOT Mar 2, 2025, 5:10 AM

#

Original message from @fleet bridge - Moved from #general message

#

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

halcyon citrus Mar 2, 2025, 5:11 AM

#

Hey @fleet bridge

You should pass existing members in for sure. The update function does not support atomic updates, so if you were to pass only a single member it would overwrite it to be that member only

fleet bridge Mar 2, 2025, 5:17 AM

#

What if the members grow quite a bit ? Isn't this going to cause performance problems?

I guess I should create a collection myself like users_teams for the relation itself to solve this problem, right ?

halcyon citrus Mar 2, 2025, 5:21 AM

#

Yep, if you anticipate it growing to a point of where it 'll be unmanagable as a field, then I would agree with you

fleet bridge Mar 2, 2025, 5:25 AM

#

thanks a lot

halcyon citrus Mar 2, 2025, 5:26 AM

#

My pleasure, have fun with it!

#Optimizing Member Updates in Teams Collection

Documentation: