Forum Discussion
tristaanogre
14 years agoEsteemed Contributor
Name mapping is a good feature but only problem is, if I create a name mapping with only NativeClrObject. (That is what I get when I run record and play). Name as search criteria at times my object search fails. So even if the object is loaded, still I get a response of object not found error. When I debugged from the node object and drilled down to child/child ... hierarchy the object is there still I use to get this error. But if give multiple search criteria like "clrClassName, Name and Index, then I am not facing such errors. So to map each object with these criteria has become more time consuming for me.
This is actually best practice, really, when using NameMapping. To use only a single property for mapping, especially if there are multiple objects that may share that property value, is going to generate any number of problems with object identification. The more properties you can use, the better chance of creating a unique mapping.
To help out with the mapping, you can create NameMapping templates that, when you map an object, it automatically selects certain criteria, speeding up your process.