I see a similar situation in SoapUI 2.0.2 this afternoon -- the XML in my Test Step includes a Property Reference "${xactId}", where the 'xactId' property itself has the value "qatest_1234", and is defined at the TestCase level.
However, the XML that actually arrives at the server has the same string as the TestStep -- i.e., " ${xactId}" -- instead of the substituted value that I was expecting: " qatest_1234".
I am still a newbie -- have I accidentally set a flag that turns off Property Expansion? Or perhaps I don't have my scope set correctly? (I have tried this using "${#TestCase"xactId}", with exactly the same outcome.)
