The parent object was not found: NameMapping.Sys While running the scripts in different machien

Question

My automation scripts working fine in the machine where the name mapping is Done.But the same fails in all other machines.Its because the sys object properties are different in other machine. How can resolve this issue?.Please fidn the screen shot after importing the scripts in new machines. Sys properties become blank

wamboo · Answer

Hi, use NameMapping condition:
&nbsp;
https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/conditional-mapping-criteria.html
&nbsp;
make a: OR, AND condition for differnet values of that object.

smithanair · Answer

Name mapping condition i have already tried. But its failing because the sys is not available. Please find the screen shot below&nbsp;

sonya_m · Answer

Thank you Wamboo!
&nbsp;
Hi&nbsp;smithanair, I found a couple of threads that might help:
&nbsp;
https://community.smartbear.com/t5/TestComplete-Desktop-Testing/The-object-quot-Sys-quot-does-not-exist/m-p/207522
https://community.smartbear.com/t5/TestComplete-Desktop-Testing/The-object-quot-Sys-quot-does-not-exist/m-p/207522
&nbsp;

Forum Discussion

The parent object was not found: NameMapping.Sys While running the scripts in different machien

Related Content

Every time I map an object, an entirely new Sys hierarchy is created in NameMapping. Please help.

Soap TestSuite runs with different configurations - ReadyApi

run testcase from different testsuite from CLI

Running tests in different locals

How to run Keyword tests in different urls.

Recent Discussions

Onscreen Object Selector Slowness

aqObject.CheckProperty() slowness

Problem with generated data table and keyword test

WebView2 support does not work

System checks for Object for every test

Forum Discussion

The parent object was not found: NameMapping.​Sys While running the scripts in different machien

The parent object was not found: NameMapping.Sys While running the scripts in different machien