Prerequisites

• •The source primary keys of records don't contain a slash (/), backslash (\), period (.), percentage (%), semicolon (;), or double quotation mark (").
The source primary keys can contain the following characters:
~!'={}|:@#$^&*()-_+,<>?`
• •The source primary key can contain 255 characters. If the source primary key contains more than 255 characters, the additional characters are truncated.
• •The source primary keys of the field groups don't contain special characters other than a colon (:), hyphen (-), pipe (|), or underscore (_).
• •The field values don't contain a single backslash (\). You can use a double backslash (\\). If the existing field values in the Business 360 data store contain a single backslash (\), contact Informatica Global Customer Support.
• •The CSV file that you import contains supported and valid population names. You can't import records that contain invalid population names. For the list of populations that you can use, contact your administrator.
• •The CSV file that you import doesn't contain business IDs, as you can't use business IDs to import business entity records.
• •The population names in the CSV file are in lowercase.
• •If the CSV file contains records to exclude from the match process, the NotReadyForMatch column in the file must be set to True. All the records that don't contain any value for this column participate in the match process.
• •If the CSV file contains double field type values greater than 300 digits, the import process considers the first 15 digits, converts the consecutive 300 digits into the exponential format, and ignores the remaining digits.
• •When you import decimal values, you must consider the following guidelines:
• - The values must conform to the defined precision and scale.
• - The total number of digits before the decimal point must be lesser than or equal to the difference between the precision and the scale.
The following table describes the sample success and failure scenarios when you import decimal values:

Precision	Scale	Decimal Value	Result
8	3	87654.321	Imports the decimal value because the value is within the default precision and the defined scale.
3	2	1234.5	Rejects the value because the number of digits before the decimal point isn't lesser than or equal to the difference between the precision and the scale.
5	2	1.345	Rejects the value because the number of digits after the decimal point isn't lesser than or equal to the difference between the precision and the scale.
5	5	1.345	The import process rejects the value because the digits before the decimal point is not within the difference between the precision and scale. The different between the precision and scale is 0.

• •When you specify the upsert operation type in the CSV file or select create or overwrite records in the user interface, the import process considers attribute-level privileges to add or update field values.
• •When you specify the delete operation type in the CSV file, the import process doesn't consider the attribute-level privileges.
• •To import hierarchy data, the CSV file must contain the parent and child records that you want to import.
For example, if you have a hierarchy with a relationship defined from the Organization to the Person business entity, you can import the related records in bulk from a CSV file into the hierarchy.
• •You can specify multiple populations for the records in the CSV file.