Category:Map Files
Last Updated:2011-08-18
A Custom LIST Map file allows you to change any aspect of how the sync creates new GROUP objects on the destination directory for this connection. LIST Map Files are directory type specific. The source and destination directory type of the connection must be appropriate for a specifically configured LIST Map file. (i.e. A Notes-to-AD map file may not be used in an AD-to-AD connection.)
The most common use for a Custom LIST Map is to customize how attributes are mapped between systems. It is also possible to customize the sync container, so that your synced Group objects are created in a different container than your synced contacts. For more help on Custom mapping syntax, click the Help button on the Custom Map tab of your connection.
Creating a Custom LIST Map File
1. From the UnitySync UI, select your connection, then click the Custom Map tab.
2. Enter a name in the LIST Map parameter, then click Create.
3. Make your changes to the map file.
4. Click Save to save your map file changes.
5. Click Apply to save the name of the custom map file in the Custom Map tab.
A Note about using a custom DN mapping to change your sync container for Groups:
The ~struct~ is a required part of the syntax. This value will be the structure specified by PlacementDN and/or StructName.
You may not remove ~struct~ and try to hard code the entire DN mapping, such as:
dn=cn=~component0~,ou=Groups,dc=domain,dc=test
This syntax will result in inaccurate structure.
However, you MAY customize the DN to ADD structure where ~struct~ is a common root of the destination sync container for both Contacts and Groups. (Create a custom OBJECT map file to customize the DN for Contacts.)
i.e.
Placement DN is: dc=domain,dc=test
Custom Group (List) DN mapping is: dn=cn=~component0~,ou=Groups,~struct~
Custom Contact (Object) DN mapping: dn=cn=~mail#64~,ou=Contacts,~struct~
Your Groups will be synced to: ou=Groups,dc=domain,dc=test
Your Contacts will be synced to: ou=Contacts,dc=domain,dc=test