|Maintenance and Troubleshooting||<<||>>|
There are three types of separators you can use with directory import and directory export: column, quote, and property. For descriptions, see "Selecting Separators and Character Sets" earlier in this chapter.
When you import or export multivalued properties, Microsoft Exchange Server quotes the entire multivalued property. Embedded, multivalued property separator characters are prefixed with a backslash (\) character. For example, a multivalued property with values "v,1", "v,2", and "v,3", is exported as:
A multivalued property with values "v%1", "v,2", and "v,3", is exported as:
For example, the multivalued property of an exported proxy address might look like the following. The CUSTOM: proxy address (Black, Maria at \\SANFRANCISCO01) has an embedded comma and embedded backslashes. The comma is the default multivalued attibute separator, and the backslash is the literal character introducer. Because of the presence of embedded commas, the entire multivalued proxy addresses property is quoted, and each of the two embedded backslashes is introduced by a backslash character.
"CCMAIL:Black, Maria at California%CUSTOM:Black, Maria at \\\\SANFRANCISCO01%MS:FERGUSONBA/NAMERICA-W/MARIAB%SMTP:MariaB@ California.Ferguson&Bardell.com%X400:c=US;a= ;p=Ferguson ? Barde;o=California;s=Black;g=Maria;"
The following example shows the Members multivalued property of an exported distribution list, which shows the distinguished names of the members of the distribution list. Because there are no embedded special characters in the string (for example, commas and backslashes), the property is not quoted.
Using .Csv Files Generated by Microsoft Exchange Server Version 4.0
In Microsoft Exchange Server version 4.0, if a multivalued property contained embedded separators (for example, commas and tabs), the property values making up the multivalued property were quoted individually. If Microsoft Excel was then used to edit the exported data file, the quotes embedded in the multivalued property value string were not recognized, and the property would be incorrectly split across several Microsoft Excel cells.
Import files generated for use with Microsoft Exchange Server version 4.0 are compatible with Microsoft Exchange Server version 5.5, with the following exceptions: