"You do not have access to this resource"

Getting the following error trying to execute the following query:

mutation{
         updateActiveOffer(id: "5d7d7476c9bb8714baa52d5a", data : { quantity:2 }){
	quantity
            offer{
              name
            }
	}
}

  "errors": [
    {
      "message": "You do not have access to this resource",
      "name": "AccessDeniedError",
      "time_thrown": "2019-09-15T01:39:39.829Z",
      "data": {
        "type": "mutation",
        "target": "updateActivedOffer"
      },
      "path": [
        "updateActivedOffer"
      ],
      "uid": "ck0kbaoqd00021m3a900r0j1w"
    }
  ],
  "data": {
    "updateActivedOffer": null
  }
}

I’ve removed any authStrategy and here is the list’s configaration-

exports.ActiveOffers = {
    fields: {
        offer: {
            type: Relationship,
            ref: 'Offer',
            many: false
        },
        assosciatedUser: { type: Relationship, ref: 'User', many: false },
        // expires: { type: DateTime },
        quantity: { type: Integer },
        slug: {
            type: Slug,
            from: 'offer'
        },

    },
    access: {
        create: true,
        read: true,
        update: true,
        delete: true,
    },
    labelResolver: async (item) => {
        return `${item.offer} <${item.quantity}>`
    },
}

[MadeByMike]

Thanks! I’ll make an issue for a better error message and close this one. @Nakzz Thanks for your help in reporting issues recently. I hope this resolves it for you and you’re able to get your project running.

If you need more help with this, or other general questions jump onto the community slack channel: http://community.keystonejs.com I’m usually hanging around there and will be able to offer more help.

[jesstelford]

I’m guessing this fails because there is no string representation for the offer? Perhaps you are not allowed to use ‘from’ on Relationships?

This is correct; the Slug.from setting should point to a field which has a text value. We could do better at attempting to resolve that and throw a more useful error.

As it stands, the configuration for ActiveOffers.slug should probably be removed.