yeah, the variables or tables creates the issue of having to pick it out of the data. Would be nice to have a way to create a high level variable - like the run property, but can be changed and referenced the entire flow without having to pass it along with data :)
for now, i will just use the RunDate_FileSafe :) thanks Adrian!
------------------------------
Geoff Goldsmith
Windstream Communications
Little Rock AR
------------------------------
Original Message:
Sent: 05-21-2025 10:07
From: Adrian Williams
Subject: Change the value of a run property.. at runtime?
Run property values are considered literals / constants and are evaluated at the time the data flow was initialized prior to being executed. The values cannot be updated from within a data flow.
Obviously, you could create a variable within a node and set it's initial value to that from a Run property and then later update that variable's value. However, the scope of that variable would only be in the node that defined it. You could output the updated value in an output field but there is no way to 'broadcast' the updated value so it is available to other (unconnected) nodes within the data flow.
You can pass a variable from a Parent data flow into a Child data flow using the Execute Data node. This variable would then be available within the Child data flow as, effectively, a Run property.
Depending on the situation, you could alternatively write a value to an external data store (DB table, a temporary file (.brd file), etc) and then read in the value as required.
------------------------------
Adrian Williams
*Precisely Software Inc.
Original Message:
Sent: 05-20-2025 14:02
From: Geoff Goldsmith
Subject: Change the value of a run property.. at runtime?
is there a way to update/change the value of a run property.. during runtime?
like..
node.properties('rundate') = '5/4/202'
so late when {{^rundate^}} is used it has that date?
thanks!
------------------------------
Geoff Goldsmith
Windstream Communications
Little Rock AR
------------------------------