Can't access environment variables in subflow (Node-RED)

[jacobc1]

I am making a subflow that will set a message property but it uses an environment variable from the subflow to determine if it should set a message, but every time I call env.get() I get this error: “TypeError: Object.hasOwn is not a function”

I am running Node-RED version 3.1.7, any help would be greatly appreciated!

// Sets msg.isCombined = true IF combined inlet is open
// Sets msg.apm to the APM with the open inlet

const GAS_ANALYZER_NAME = env.get("GAS_ANALYZER_NAME"); // Causes error

for (let i = 0; i < msg.digitalOutputs.length; i++) {
    const digitalOutput = msg.digitalOutputs[i];

    if (digitalOutput.name.includes(GAS_ANALYZER_NAME))
        if (digitalOutput.value) {
            const tagParts = digitalOutput.name.split("_");
            const apmParts = tagParts[1].split("APM");

            if (apmParts.length == 2)
                msg.apm = parseInt(apmParts[1]); // Get APM ID
            else
                msg.isCombined = true; // Using combined inlet
            break;
        }
}

return msg;

[Beno]

I think is this the same issue as described here?

Node-red subflow compatibility issue

I recently upgraded my EPIC PR1 fw from 3.4.4 to 3.6.0. Unfortunately, my node-red application stopped working when moving from node-red version 2.2.2 to 3.1.7. I was able to isolate the error to one of my subflows that uses env.get("key") inside a function node to access the subflow properties. The env.get function simply doesn’t work after upgrading fw (node-red version). I created a simple flow as an example. [main_flow] [subflow] [subflow_props] A simple flow that prints the subflo…

[jacobc1]

Thank you! I did not realize there was already a post on this, it appears to be the same exact issue I am having