I have a workset configuration that sets some project variables,
#========================================================================= SA_PROJECT_YEAR = 2022\VISION_PRJ = 122.0030.01 _USTN_PROJECTDESCR = VISION_PRJ_USTN_PROJECTNAME = VISION_PRJ
As you can see, Vision_PRJ is defined and _USTN_PROJECTDESCR and _USTN_PROJECTNAME should take that value. When running a debug I get the following
Processing macro file [e:\Configuration\WorkSpaces\2022\WorkSets\122.0030.01.cfg] (WorkSet): SA_PROJECT_YEAR=2022\ [2022\] (WorkSet): VISION_PRJ=122.0030.01 [122.0030.01] (WorkSet): _USTN_PROJECTDESCR=VISION_PRJ [VISION_PRJ] (WorkSet): _USTN_PROJECTNAME=VISION_PRJ [VISION_PRJ]
Why wouldn't the variable VISION_PRJ be parsed to the _USTN_PROJECTDESCR and _USTN_PROJECTNAME values?
This is in ORD 2022 Release 1
Thanks
To use the value of a configuration variable to set another variable, you actually need to add the code to "expand" the variable.
instead of just using the variable name VISION_PRJ in _USTN_PROJECTDESCR (etc.) enclose it like $(VISION_PRJ).
This tells ORD to use the value defined for that variable. There's more information about this in the Help.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Answer Verified By: SteveMeyer
Thanks Mary, it has been working for 3 year and with the new release, it no longer does. I guess I need to read help more often.
I'm actually surprised it worked without the $( ) because that's been standard CFG file code for decades.There is also ${ } which reads the variable at different points in processing, but I generally haven't needed that variation.
I'm glad we could get it working for you.