Updating a binary field of a node causes 404 on Webroot API

Gentics Mesh Version, operating system, or hardware.

• v1.4.3

Problem

Updating a binary field in a node where the segmentField is another field makes the node unable to be found via the webroot API.

Reproducer

1. Create this schema:

{
    "description": "asset",
    "name": "Asset",
    "displayField": "name",
    "segmentField": "slug",
    "fields": [
    {
        "name": "content",
        "label": "Content",
        "required": false,
        "type": "binary"
    },
    {
        "name": "name",
        "label": "Name",
        "required": true,
        "type": "string"
    },
    {
        "name": "slug",
        "label": "Slug",
        "required": true,
        "type": "string"
    }]
}

2. Create a node of that schema
3. Verify that the node is accessible via webroot
4. Upload a binary to that node
5. Try again to fetch the node via webroot

Expected behaviour and actual behaviour

I expect the node to be found after updating the binary field. Instead I receive a 404 error.

Reproduce the failure with the Asset schema from the issue: use a separate slug segmentField, verify the node through the Webroot API, upload a binary to content, and request it again. Compare the Webroot lookup before and after the binary update, then confirm that the node remains accessible after the fix.