Node-red-contrib-json-db DataError: The Data Path can't be empty

Hello,
I have used this node before without issue, however when I run it in the latest docker container I am getting this error message. DataError: The Data Path can't be empty. If I test it outside a docker it works fine, but soon as it is in a docker container the error message appears.
Here is the example flow I have been using.

[
    {
        "id": "50cbab180f96f2ec",
        "type": "DataIn",
        "z": "54e00243c63a0667",
        "collection": "dd241ba0efa3c601",
        "name": "",
        "update": false,
        "topic": "",
        "x": 910,
        "y": 720,
        "wires": []
    },
    {
        "id": "b534ad217423053c",
        "type": "DataOut",
        "z": "54e00243c63a0667",
        "collection": "dd241ba0efa3c601",
        "name": "",
        "topic": "",
        "error": false,
        "x": 920,
        "y": 780,
        "wires": [
            [
                "668fc139d5107d1c"
            ]
        ]
    },
    {
        "id": "bd22848411e9cc13",
        "type": "inject",
        "z": "54e00243c63a0667",
        "name": "",
        "props": [
            {
                "p": "payload"
            },
            {
                "p": "datapath",
                "v": "/client",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 720,
        "y": 720,
        "wires": [
            [
                "50cbab180f96f2ec"
            ]
        ]
    },
    {
        "id": "ad69d02b37b5abcf",
        "type": "inject",
        "z": "54e00243c63a0667",
        "name": "",
        "props": [
            {
                "p": "datapath",
                "v": "/",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "x": 710,
        "y": 780,
        "wires": [
            [
                "b534ad217423053c"
            ]
        ]
    },
    {
        "id": "668fc139d5107d1c",
        "type": "debug",
        "z": "54e00243c63a0667",
        "name": "debug 2",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": true,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "payload",
        "statusType": "auto",
        "x": 1100,
        "y": 780,
        "wires": []
    },
    {
        "id": "dd241ba0efa3c601",
        "type": "json-db-collection",
        "name": "",
        "collection": "workplace",
        "save": true
    }
]

I thought this could be a permission issue so I did a chmod 777 to the JsonDB folder and file that was created, but still no luck. Does anyone have any ideas as to why this flow works on a stand alone version but not in a docker container?
Thanks

Well, I tried in docker and it failed.
But so did the example delivered with it, too.

The node has not been updated in 6 years and most of it is way older...

I guess the node simply is broken.

1 Like

Thanks for testing it out man, I tried what looks to be another clone and it looks to work. json-db-node-red So if anyone else has this issue just do not use that repo and use this one.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.