Forum Discussion
I found a possible workaround for the issue: By redefining again the value of the variable to the one that was already set (i.e. in my case the @username list) in the request body after Step 7 the correct values are taken.
Note: The same issue was encountered while using a .CVS file as data source.
Hi,
According to the description, it looks like you've faced a known LoadComplete 4 issue. So, if you are using LoadComplete 4.0 or LoadComplete 4.10, please try upgrading to LoadComplete 4.20 - the issue is fixed there.
- RVS9 years agoNew Contributor
I can indeed confirm that I utilised the release 4.10.1780 to set up the parameter values.
Kr,RVS
- NehaA9 years agoNew Member
Hi Alexey,
I am facing this issue even after upgrading to 4.20 version. I followed the same steps as mentioned in ‘https://support.smartbear.com/viewarticle/78497/’ and instead of retrieving variable from excel, I have used a constant LoadComplete variable(string).
let me know if anything else needs to be done in the newer version for this to work
Thanks,
Neha
- AlexeyKryuchkov9 years agoSmartBear Alumni (Retired)
Hi,
I think that we’ll need to analyze your test project. Please pack it as it is described in this article, create a new Customer Care case and attach the archive to it.
Related Content
- 2 years agoAnonymous
Recent Discussions
- 3 years ago
- 3 years ago
- 4 years ago