Why isn't the getVariableAsString the same in Node.js

[jan_suhr]

I'm glad that we finally got the getVariableAsString in to the Node.js but why is it so limited?

In Legacy it can handle all of the Switch variables but with Node.js it will only accept Metadata variables.

This mean that we still have to do some workarounds to get all the other variables in to a script.

[freddyp]

It is not only the Metadata variables, but indeed not everything is covered as in legacy scripting. The technical background is complex and it will take a lot of time to port everything, but we did not want to wait until everything was available. From the feedback we got from partners and customers the Metadata variables were the most often used ones and also the ones that are the most difficult to substitute by other code.

You are always welcome to share the variables that you would like to see implemented next.

[jan_suhr]

I needed some of the Stats variables for a Script Expression.

I solved it by setting it as a Private Data and in the script picked up the value.

I think that the most needed would be from the Job and Stats groups

[sander]

+ 1 for the Jobs and Stats groups!

My personal priority would be jobs to be implemented first haha