Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: timonkBishop,
Good Day.
I think the key to your solution lies in the mechanic of parameter substitution. Remember that you can use BRAINScript parameter textual substitution to setup many nodes that can be altered by only changing the value of the root parameter.
For example:
node:Directory_List
bretype:core::Directory List
editor:sortkey=4c0f8c8612442580
output:@40fd2c747c2b1c0a/=
prop:DirectoryName=c:\temp\{{^DATE^}}
prop:Pattern={{^DATE^}}DATAFILE*.txt
editor:XY=280,380
end:Directory_List
The code above is a Directory List node, which you are aware of. This node has the benefit of taking standard wildcards as well as parameters.
In my graph I declared a graph parameter DATE. Then I setup test files: "20100609DATAFILEasefes.txt" and "20100610DATAFILE12345.txt" in the directories "20100609", "20100610". Using the node above, and plugging in the date value into the graph parameter, the Directory List node produced the correct test file. BRAINSscript substituted in the DATE value, and the node took the wildcard * to handle the random element. I then linked it to the .CSV node and used FilenameExpr to load the data (just use the name of the field from the Directory List output:'FileName').
This is, I think, one possible solution to your situation.
Regards
Timon Koufopoulos
MDA Support.