Bulk import domain entries

The input is CSV with a header row that specifies the order of these columns: lookup_nm description folder_path name value or

On each row in the lookup_nm column, the name of a reference data domain is specified. The description column is the description of the domain. In the folder_path column, the containing folder of the domain is specified. A valid folder value: begins with the / character has no consecutive / characters does not end in the / character

The name column holds a key of the domain entry. The value column holds a value of the domain entry. Only the description column can be blank. Labels cannot be applied to the key and value from this operation. The updateReferenceDataDomainContent operation can be used instead to add the labels. The disabled column is used by the value list. It is a boolean value, which indicates whether the entry is disabled. The entity_sq_no is used only by the value list. It points out the order of the entry within the entries of the value list. The type_nm is the type name of the object. It could be "lookup" or "valueList". The bulk import creates the domain or value list in the supplied folder if an identically named domain or value list does not already exist. If the domain or value list already exists, then the entries in the latest domain or value list content are deleted and the entries from the input CSV are added. If the latest domain or value list content has the "production" status, the "delete" and "add" operations cannot be done. Each domain or value list in a folder has a unique name. However, the same domain or value list name can be used in another folder.

The input CSV is processed in the order it is received. All contiguous rows with the same domain name and folder path are considered one section. Those rows are processed according to the description above. It is possible to have the same domain name and folder path appearing in non-consecutive sections. In that case, the subsequent section is considered a replacement of the domain entries from the previous section. The service tries to process as many rows as possible.

The output is a multipart/mixed response body. The boundary string of each part is identified in the Content-Type response header. There are three parts in this response. The first part is for the accepted CSV (header Content-ID: Accepted-CSV). Each row that was successfully imported is included here. As soon as a domain is processed, the successful rows are streamed back. The second part is for the rejected CSV (header Content-ID:Rejected-CSV). Each CSV row that failed processing is identified here. It is in CSV format with the following column order: record number in the entire CSV input, lookup_nm, description, folder_path, name, value, and error message. The third part is for global issues (header Content-ID: Global-Issue). It is in CSV format with the following column order: lookup_nm and error message. The message conveys the error at the domain level that prevents any CSV importing. An example would be the lack of permissions to create the containing folder. If this error applies to the entire input, the lookup_nm column has an asterisk. If this error applies to only a domain, then the domain is identified in the lookup_nm column.