Examples: User profile attribute change files
After you are enabled to use the integration server, and are familiar with file naming and attribute specification requirements, you can create user profile attribute change files for updating profile information for users in your organization.
Review Creating user profile attribute change files before proceeding.
The file header specifies the operation field names as they are defined in the first column of Table 2 in Creating user profile attribute change files (case insensitive). The remaining lines define values for the corresponding fields. Each line must end with an appropriate carriage return or line feed character. On Windows use \r\n (0x0D 0x0A) and on UNIX or Linux use \n (0xA). While the integration server can process files with either line ending format, use the TEXT transfer format to ensure that proper line endings are sent to and received from the intermediary FTP server.
- Add the relevant field data in the correct CSV field order as shown in the following examples. Reference Table 2 in Creating user profile attribute change files for additional information.
- Use a UTF-8 character set.
- Add an empty value for an optional or non-applicable field by using consecutive commas.
- Encode a zero length string for a field as “”.
- Surround field values with double quotation marks ("") if the
value contains any commas or double quotation mark ("") characters,
or contains spaces at the beginning or end of the value. Other field
values can optionally be surrounded by double quotation marks (""):
- Field values can be surrounded by double quotation marks ("") regardless of the characters in the field.
- Double quotation marks ("") must be used for field values that include a comma.
- Double quotation marks ("") must be used for field values that have one or more spaces at the beginning or end of the value.
- Encode a double quotation mark ("") character by using a pair of double quotation marks ("") characters, for example ...,"John ""that guy"" Doe", ...
- An update operation that contains an empty field value (for example ,,) leaves the field set to its existing value.
- An update that specfiies a zero length string replaces the field value with a zero length string.
- Operation names are not case-sensitive.
- You can omit trailing commas at the end of a statement. For example,
the following two statements yield the same result:
joseph_lu@bluebox.lotus.com,update, N,"some description", joseph_lu@bluebox.lotus.com,update, N,"some description",,,,,,,,,,,,, - You can omit field names, and commas, at the end of a statement
if they are not required for the operation. For example, if no fields
are needed past description, only values for the
following fields are sufficient:
emailAddress,action, isManager, description
emailAddress,action,isManager,managerEmail,jobResp
branney@renovations.com,update,Y,marmond@renovations.com,Lead System Administrator
sdaryn@renovations.com,update,N,bgossens@renovations.com,Promotions Coordinator
emailAddress,action, isManager, description, experience, telephoneNumber, mobileNumber, faxNumber, phone1, phone2, phone3, address1, address2, address3, address4, item1, item2, item3, item4, item5, item6, item7, item8, item9, item10
joseph_lu@bluebox.lotus.com,update, N,"some description","user experience rich text",123-456-7890,345-678-9012,789-012-345,"","","","550 King Street, Littleton, MA","","","","item1 value","","","","","","","","","item10 values"