Errors and rejected lines when importing data via APIs

The responses and dumps will be different, depending on what you are trying to import.

Importing into a module: having the same code in the source will automatically aggregate data based on the code.
Importing into a list: lines using the same code will be considered duplicates.

Dump file formats depend on the type of import they are targeting: line items or lists.

Import into lists: An additional column will help distinguish if the line is the first error occurrence.
Additional and similar errors are considered to be "ignored," and are combined with the first-occurrence error. These represent the "ignored" lines of error.

There are a number of scenarios that can occur when an import creates a dump file.

Import into a module

In the module shown above, you have:

Time: May 17 (filtered for simplicity)
4 line items
- 2 editable: Unit Sales by period, Amount to add
- 2 calculated: Unit Sales, Current Alloc (cannot receive data)
2 list members: MSFTE and GOOGLA

To update this module, you will need to import data, as opposed to importing master data.

'Failed' error message

Let's say that the month for one line has a spelling error ('May' misspelled as 'Nay').

During import, you will receive a "Failed" error message:

When importing data into a module, if an identifier is invalid, the line containing this error will be listed in the dump of that action.

"Ignored" error message

There are two possibilities that might produce an "Ignored" error message.

This scenario occurs when you're conducting an import into calculated line items.

2. This scenario occurs when you're conducting an import into elements that are already subject to aggregation.

Let’s try to import data into a parent. Choose 'Q2 FY17' as parent of a time member.

You will receive this response and no dump:

Import via API into a module

Now let's see what happens when you import data into a module with the incorrect mapping (spelling error 'Nay 17') through API calls.

Rejected lines through APIs will only be generated for the lines that have incorrect identifiers (such as 'Nay 17' instead of 'May 17').

'Ignored' lines won’t be mentioned for line items calculated or consolidated in a hierarchy.

Import into a list

Let's try to update the list that contains the two elements, MSFTE and GOOGLA.

We will be targeting master data (lists and properties) and using a "code only" import.

Import into a list: no errors

If you use the import file below, no issues will come up.

The API will send back that two elements were updated (even though no change occurred).

Import into a list: duplicated code

This import file contains duplicated code. Line 4 is using an already-used code (from Line 3).

In this case, you'll receive a warning (not an error!) that a row has already been processed with that key.

Why a warning? Because the first occurrence of the code has been successfully processed, and technically, the import did go through and changes were made.

This is the dump file with the rejected lines:

Import into a list: 'Ignored' error message

Duplicated line added (with error):

In the API dump log, you will get an error line as well as a rejected line:

If another duplicated line is added...

...you'll get a second rejected line:

When you import a list, if an error line is repeated many times, you'll see an error in the first line and the other lines that are similar will be rejected.

Import into a list: invalid code

If you use this import file, you will generate a failure:

In the dump file below, you can see the rejected lines:

The '_Status_' column isn't empty:

title