Change in DT 5.6 presenting the method return value from [1] to true?
We have upgraded from dynaTrace5.5.0.5562 to 5.6.0.5713 and experience a few of our BTs configured to capture return values are not working any more.
Example with easyTravel:
We have created a sensor to capture return value for com.dynatrace.easytravel.business.webservice.AuthenticationService
In sensor deployment -> Details (for the Businessbackend) we can see returns are Boolean
In Purepath tree for DT 5.5 return value column show method return value as "[ 1 ]" (without spaces but not able to write it that way here....)
In Purepath tree for DT 5.6 return value column show method return value as "true"
In DT 5.5 we had to configure measure with return value match "contain "1" and it worked
In DT 5.6 we had to update the measure to return value match "contain/eaquals true"
As I see it this result in all measures and BT reporting on return value have to to be updated manually.
Is this change intended and working as designed? I believe there are several installations that will be upgraded to DT 5.6 having configured to capture and report on this return value. From my point of view this is a bigger change... Is it mentioned anywhere?
Is there any easy way to update all measures to reflect the change in presentation of the value or do you have to update each one manually?
-Tore
hi Tore,
by now I can't imagine which behavioral change you're referring to. I just tried it with dynaTrace 5.5 and got the expected boolean result "true":
could you please attach both exported PurePaths from dynaTrace 5.5 and 5.6, so we can take a look at this.
thx, Christian
I have to restart my two VMs to reproduce it, in the mean time I send you the screenshoots of it 
The one with Value "true"=DT5.6 and value"[1]"= DT 5.5
Hi Christian,
Attached the two DTS files for exporting the purepath in DT 5.5 and 5.6…
The 5.5 is the base for upgrade to 5.6, we just cloned the VM before we did the upgrade.
Looking forward to your answer
-Tore
hi Tore,
I see your point and can also reproduce it locally now with 5.5. however, I did not find anyone so far who could tell me more about the changed behavior (and especially the wrong behavior in 5.5). I'll keep you posted, as soon as I figure out more.
best, Christian
Looking forward to it, and a way to check what measures do have this return value without opening every measure manually whould be nice and more time efficient
Have a nice weekend!
-Tore
hi Tore,
sorry, just realized I did not write back here.
basically it's like that, that we handled the return value in a wrong way on the dynaTrace 5.5 Server/Client and this was fixed in 5.6.
best, Christian
