Using xlsx to json node, cannot change file after being used

I am using this fairly new node xlsx to json node, the idea of the flow is to load a file, to something with the data, and have the capability of opening a different file to repeat the process

the problem here is that once the node is used, with a certain file, for example file 1, on the next run, trying to load file 2, it will still open file 1, even when the msg.filepath input has been properly changed.

I think this is something to do with the node itself, unfortunately I cannot seem to find the place to locate the particular contributor, to provide feedback.

[
    {
        "id": "3e06b3433b7a20ad",
        "type": "tab",
        "label": "Flow 2",
        "disabled": false,
        "info": "",
        "env": []
    },
    {
        "id": "d3e2d31e4bca1883",
        "type": "inject",
        "z": "3e06b3433b7a20ad",
        "name": "",
        "props": [
            {
                "p": "payload"
            },
            {
                "p": "topic",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 120,
        "y": 120,
        "wires": [
            [
                "195eb091a12ec3eb"
            ]
        ]
    },
    {
        "id": "195eb091a12ec3eb",
        "type": "change",
        "z": "3e06b3433b7a20ad",
        "name": "",
        "rules": [
            {
                "t": "set",
                "p": "filepath",
                "pt": "msg",
                "to": "Procedure_filepath",
                "tot": "global"
            }
        ],
        "action": "",
        "property": "",
        "from": "",
        "to": "",
        "reg": false,
        "x": 360,
        "y": 120,
        "wires": [
            [
                "8970825e3063a997"
            ]
        ]
    },
    {
        "id": "912504b8ae2aeb06",
        "type": "change",
        "z": "3e06b3433b7a20ad",
        "name": "",
        "rules": [
            {
                "t": "set",
                "p": "Procedure_Selected",
                "pt": "global",
                "to": "payload",
                "tot": "msg"
            }
        ],
        "action": "",
        "property": "",
        "from": "",
        "to": "",
        "reg": false,
        "x": 830,
        "y": 120,
        "wires": [
            [
                "565fa3687b2cd82d"
            ]
        ]
    },
    {
        "id": "565fa3687b2cd82d",
        "type": "debug",
        "z": "3e06b3433b7a20ad",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 1090,
        "y": 100,
        "wires": []
    },
    {
        "id": "8970825e3063a997",
        "type": "XLSX-to-json",
        "z": "3e06b3433b7a20ad",
        "name": "xlsx to json",
        "filepath": "msg.filepath",
        "rangecell": "",
        "columnkey": "",
        "sheet": "",
        "x": 570,
        "y": 180,
        "wires": [
            [
                "912504b8ae2aeb06"
            ]
        ]
    }
]

Normally, when you pass in a configuration option for a node, you should leave that option blank in the node. So try this, blank out the option in the node
Screen Shot 2022-06-10 at 3.26.53 AM

Thanks for the quick feedback

Actually that is how I was using it, I probably left it there while trying different things.

I completed the project with a CSV to JSON node, but I certainly liked the functionality of the XLSX version,

Do you know how to provide feedback to de developer? To keep improving the nodes

Regards

You can use npm owner ls {name of node on npm} to show the email of the node's owner if they don't already provide an Issues page where you can raise suggestions.