Description
Are you setting up an import mapping and have you arrived at the behavior & identifiers step? Then this article is for you. By way of example, imagine you would like to import spreadsheet with a list of requirements as displayed in the example below:
The settings for identifying, and the behavior of not found and multiple found will help you to get the desired result out of your import mapping.
Step-by-step explanation
1. Identifying behavior
First we need to determine if and how we want to identify each column. In the example above, we might say that the external ID's are the best way to determine what levvr needs to do with the data on each row.
If we identify on ID, then that means that when the import is ran, levvr will search for requirements that have that exact ID, before it will apply the selected behavior which is explained next. In this example, we could also choose to search for requirement name in order to determine whether this piece of data already exists, or even both!
Note: next to identifying on fields of a node itself, we can also identify on related nodes to see if relationships between 2 cells in a spreadsheet already exist!
2. Not found behavior
The not found behavior defines, what happens to the row in case levvr was not able find the corresponding requirement! You can choose from three different kinds:
Block: choose this behavior in case you know what is in your spreadsheet and are definitely not expecting requirements that can not be found. This probably means that the data in your spreadsheet is corrupt and that you first want to figure that out before running the import!
Create: choose this behavior in case you want requirements that are not found, be imported as new requirements!
Skip: choose this behavior in case you get a list of requirements where you might already have a few of them in levvr, but new ones might be added as well. A use case might be that you get an updated list of requirements from a third party so every now and then, which you use to update yours in levvr.
3. Multiple found behavior
The multiple found behavior can be set to determine what should happen with the row in the spreadsheet when the identified value is found more than once. Once again, this helps you to maintain the integrity of the data. In case you don't the same requirement to be in the list twice, select block to prevent corrupt data to be imported, else select skip.
A use case might be that when you want to import requirements and their statuses and 1 requirement occurs in row 1 and row 10, but has a different status assigned, then the status in row 1 will be overwritten with the status in row 10.