Forum Discussion
For any who are reading this, I have a newer update. I have found that 15.71 to 15.72 update is when my name mapping broke. After further investigation I found that in upgrading the version caused my mapped object to identify as other Mapped Objects. I have submitted a support ticket about this, and will update again once i have more information. For the time being i have rolled back to 15.71
I've got a reply from SmartBear Customer Care. They told me to use a workaround with the full object name. I replied to them that is not an acceptable solution. If it works before with a previous version it should work with the latest version.
- Marsha_R9 months ago
Champion Level 3
Did you try it? Did it work?
- chkwto9 months agoOccasional Contributor
Marsha_R​ It works, but I am not going spend time to fix all the code using the workaround. Just wait for a proper fix and when writing new code use the full object name