Forum Discussion
gilugopi
Contributor
I have faced same issue before. I was renaming the resource while I was already in a user defined environment. The work around suggested by Smartbear support was to switch to 'Default Environment' before renaming resource, which worked for me. Smartbear folks did acknowledge that it's a defect which they will work in future release.
If your issue is the same, try this as a work-around.
Regards,
Gilu Gopi
sclavell
8 years agoOccasional Contributor
That appears to work. Thanks for the tip!