(I am going to delete my old threads because I have a lot of word salad in those since it was so confusing.)
I am programming with the Parallel process model. I need to have a custom path string.
The short version: The TS chokes on a custom string that uses non-macro variables during the initialization. But if I ignore those errors there is no issue when I actually generate the filename at the end of a socket run.
When running the sequential model, TX will attempt to validate the final file path before your sequence executes. So if you try and specify something like "runstate.locals.XYZ" into the string, TS will error befere the start of your test. The way around this is to incorporate the $(UUTStatus" macro. When TS sees this, it won't validate your path until the end of the run, after the status has been determined. And then any variables (that exist) can be incorporated. This works fine in the sequential model.
However, when I try and run the parallel model, I get into trouble. Even with the $(UUTStatus) macro, TS will still try and pre-validate the path expression, and error if you are using variables. However, I have discovered that if you just ignore those errors everything works fine. My expression is processed at the end and all is well.
At this point, it seems that I will need to create a new model plug-in to replace NI Report Generation, and then copy that over, modifying to skip those validations. While not impossible, it's not exactly a minor endeavor either.
Before I spend time and effort on this, does anyone have any insight?
