The most common problem when mapping properties is malformed XML. You should always use an editor that recognizes XML code and which flags syntax errors. You can also quickly check that an XML file is valid by trying to open it with Microsoft Internet Explorer (MSIE). If it has an error, it will not display at all.

Errors can also be caused by defining sources or targets that do not exist, or which do not match. Note that CAD properties and aPriori attributes are case-sensitive: if your XML syntax looks correct, and the properties and attributes that you are trying to map all exist, make sure that your spelling in the XML file exactly matches the case the names.

If you encounter a mapping problem and cannot track it down, examine the aPriori log file (apriori.log). Most problems will result in an error message that can be found in this file. You can access this log from the aPriori client by clicking Help > Explore Logs Directory and then double-clicking apriori.log.