Data Synchronization Configuration Limitations

The following limitations apply to the changes that you can make to the data synchronization configuration file:

You can change the mapping of attributes within a data object. You cannot change the mapping at the object level. For example, you cannot map the CA APM Location with the CA SAM User. You can map the CA APM Location with the CA SAM Location only.
You can add columns under criteria. For example, the Contact object has User as the default Contact Type. As a result, all the data rows in the Contact object with Contact Type of User are selected for data synchronization. You can add other criteria. The following statements show a sample of how to add criteria:
```
<APMCriteria>
```
```
<Criteria apmattribute="contacttype.value" value="User" />
<Criteria apmattribute="contacttype.value" value="Analyst" />
<Criteria apmattribute="costcenter.value" value="NewCostCenter" />
```
```
</APMCriteria>
```
These statements specify the following selection criteria for data synchronization:
- All Contacts with a Contact Type equal to User or Analyst
- All Contacts with a Cost Center equal to New Cost Center
Each criteria XML node can have only one value. For example, the default criteria value for Contact Type is User. More values (for example, “Analyst” or “Employee”) can be added (or removed). However, you cannot have “Analyst, Employee” as the criteria value. Create a criteria XML node for each unique value.