Forum Discussion
In simple terms Project A uses mappings in project A not B
Even if it reffers project B.
So you should have Aliases.Process_A.obj_Parent.obj_B in project A.
You can merge Mapping of B with Mapping A link
what I do is keep common namemapping file so that project A,B, and C all refres to one file
NisHera Many thanks for your reply. The only reason why i am doing all this is this - If i keep everything in one project my Object Repository (NameMapping) becomes quite large and then i start having issues like :
- object identification
- Project takes 4-5 minutes to open.
The application is based on JAVA Swing objects. I have to populate different windows from the main windows and it's hard to specify properties to all the windows so that no object identification issues occur (or i am not good at object identification techniques). So, i thought keeping different scripts in different projects means - every script will use its own NameMapping and will have no conflicts of object identification. But i guess, that's not right. Even if i refer any script from projectB from ProjectA, it would still use NameMapping of ProjectA.
Any other solution to this problem? I am going to try merging of NameMapping with different configurations though.
Thanks for your time.
-Vik