Error: Cannot find module '@payloadcms/plugin-relationship-object-ids'

[zazz-ops]

I'm attempting to install this plugin and I'm getting a fireworks of errors.

First, when I follow the instructions in the README that say "just import and install it" I get the following error:
Error: Cannot find module '@payloadcms/plugin-relationship-object-ids'

So I thought maybe I needed to install it from npm, so I run npm install --save @payloadcms/plugin-relationship-object-ids and I get the following error:

Does this plugin work with Payload 2.8.1? If so, how do I go about utilizing it without error?

[zazz-ops]

@jmikrut Any advice on how I should go about getting this plugin to install properly via npm?

[olivier5741]

Hi there, I'm running through the same issue. I suppose the plugin payloadCMS version needs to be upgraded from 1.9.5 to 2.x.x :). I have no idea about the impact, it looks like a beforeChange hook assigned to every relationship field.

[olivier5741]

I created a draft pull request for the issue :) : #5

[Rikhart]

Hi @olivier5741 i am facingt the same issue, now i am using payload 2.12.1 also i has been tested your fork but always save as a String the relationship fields.

I am importing and using as the docs says

Exist something that i missing in the configuration or something aditiontal in the collection setup to get that my fields save as a Object Id?

Thanks for your help.

[olivier5741]

Hi @Rikhart, I forgot to commit a peer dependency that I just synced now but I don't know if it has an effect. Last time, I copy pasted the content of /dist into my project to use it and it seemed to work. I now abandonned this plugin, there were too many problems coming up. I just accepted relations (foreign key) to be a string and not an object id. Anyway, in one or two collection I had the ids being a "human comprehensive" string instead of an object id anyway :D

[olivier5741]

Some extra updates, so I'm using gatsbyjs on the same database, fairly easy to make it work with objectids as string. I'm also using Mongo Charts but there it's a pain to do relationships when foreign keys are string, you need to convert formats ...

[olivier5741]

I'm still looking for a work around to make payload happy and have the other tools happy as well. One idea is to keep Payload doing its stuff and add an extra field to hold the ObjectId. This only works if you update documents solely through Payload ...

    {
      name: 'place',
      type: 'relationship',
      relationTo: 'places',
      hasMany: false, 
    },
    {
      name: 'placeId',
      type: 'richText',
      hooks: {
        beforeChange: [({ siblingData}) => {
          if(!siblingData.place) return siblingData.place
          return new Types.ObjectId(siblingData.place)
        }]
      },
      admin: {
        hidden: true
      }
    },
`
``