Highlighted
New Member.
546 views

Parameter Naming Issues Causing Failure to Substitute at Runtime.

Has anyone had any problems where the size of the Parameter name has any affect on LoadRunners ability to substitute them at Runtime? We seem to have this issue running 9.5 - the parameter name is pCustomerClientGUID - now that doesnt' seem excessive, but for some reason LoadRunner keeps not being able to substitute it - which when it happens means going into the Parameters - clicking around a bit and then closing the Parameter window - that seems to solve it. This is all very well in VUgen, but when it happens in Controller now that's a whole new ball game as your test has already failed.

 

We have now gone through an exercise of minimizing the name size and the problem 'appears' to have gone away.

 

If anyone has had any exprerience of this under 9.5 I be grateful for any advice.

 

Cheers

1 Reply
Highlighted
Absent Member.
Absent Member.

I dont believe that its becaues of the length of the parameter, unless its 100 characters or something. something else is up, you should address this to HP support team

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.