So far, so good—I managed to do it in one day, but I'm a complete novice and come from LabView, where I can do something like this in 10 minutes... but anyway. Here's an example: my question is, is there any way to do this without a function node, especially when handling strings for the file name?
function:
msg.filename = '/home/rr/Dokumente/Logger/testloggera_' + flow.get("NowDate") + '.txt';
return msg;
You could use mustache syntax in a template node but NowDate would have to be a message property rather than a flow context variable. (Why are you using a flow context variable anyway?)
One of the big mysteries for me is the use of templates and what a mustach is—what a funny name. I've only shown an excerpt of my project here. The variable flow.NowDate is used elsewhere as a decision maker...
But thanks again, I'm coming from LabView where everything works without scripting! But LV has its quirks too... me hoppe is/was also NR is script free,
The name mustache clearly derives from it's use in this (admittedly uncommon) smiley :-{)
A really big mystery is how the ! came to be called Bang!
I've never heard of LabView. How would you concatenate the strings in that?
This is not a very Node-red approach, though of course it is possible to code it like this.
A flow context variable can be changed at any time by the arrival of a new message.
The Node-red approach would be to generate the value and attach it as a message property. Then the value is passed along the flow* and is unaffected by a new input
* Most nodes follow the rule of passing on such message properties unaffected. Some contrib nodes fail to do this.