Incorrect type. Expected pk value, received OrderedDict when updating a relationship

[schtibe]

I get this error:

{'errors': [{'detail': 'Incorrect type. Expected pk value, received '
                   'OrderedDict.',
         'source': {'pointer': '/data/attributes/title'},
         'status': '400'}]}

since commit d654c75 when I run my unit test. The data I send is

    data = {
        "data": {
            "type": "customers",
            "id":   self.lukeId,
            "relationships": {
                "title": {
                    "data": { "type": "titles", "id": "2" }
                }
            }
        }
    }

What is that change for / is my data wrong?

[jsenecal]

I would say that this commit title says it all: 'Relationships parsing are now only handled by compatible fields'

In more details: another field was introduced shortly around the time of that commit (23d0af6)

ResourceRelatedField handles the JSONAPI spec completely and should replace any related fields you might want to use - Both for performance and features.

Let me know if you need more help on this.

[schtibe]

Just noticed that I didn't mention that I send this data via PATCH.
I struggle to understand what 'compatible fields' means.

[jsenecal]

It means that the parser now only parses resource identifier objects (spec) in relationships. - for that, you need fields that understand resource identifier objects like the above ResourceRelatedField.

[jerel]

Is that error only shown for this one issue? If so perhaps we could improve the error with something like "title cannot be parsed. Are you sure the serializer uses ResourceRelatedField and the payload complies with the jsonapi.org spec?"

[jsenecal]

@jerel we would require to override ALL DRF related fields in that case as we cant get the serializers fields from the parser

[jsenecal]

@schtibe can you try to use the ResourceRelatedField and give us an update on this issue ?

[schtibe]

@jsenecal yes it seems to work, thank you!

[schtibe]

Although using ResourceRelatedField makes it mandatory, even though I added allow_null=True

[jerel]

Does your model also have the relationship set to null=True, blank=True?

[jsenecal]

Also, the setting is usually required=false on the relations field... See http://www.django-rest-framework.org/api-guide/serializers/#validation there is a note about this...

[schtibe]

It was required=false. Thanks