Other Import Considerations

FlexNet Code Insight 2019 R4

Consider the following additional behavior during import processing.

Matching File Paths

When the import process considers whether to add a file to inventory or mark it as reviewed, the absolute path of the file must match between the data file and the target project. For example, the file /ePortal-1.3/src/gettext.c—the only file belonging to “InventoryItem1” in the import data file—is considered to be a different file from /ePortal-2.0/src/gettext.c in the target project. As a result, ePortal-2.0/src/gettext.c cannot be associated with “InventoryItem1”; and, if the createEmptyInventory value is false, “InventoryItem1” is not created in the target project since it has no associated file. Additionally, ePortal-2.0/src/gettext.c will not be marked as reviewed in the target project.

In order for a file in the target project to be treated as identical to a file in the data file, the absolute paths for the two files must match in both locations. In the case above, you can ensure that the file paths match by uploading your code without the outer ePortal directory so that the absolute file paths are /src/gettext.c. Alternatively, you can manipulate the file paths in the data file to match those in the target project. For example, the file path ePortal-1.3/src/gettext.c in the data file would need to be changed to ePortal-2.0/src/gettext.c prior to performing the import. (All other file paths in the data file would need to be modified as well.)

Identical Inventory

Two inventory items are considered identical between the source and target project if they are associated with the same repository item (based on the unique combination of component-version-license, or CVL). Identical inventory is resolved during the import by overriding all fields in the target project with information from the import data file, with the exception of empty data in the data file.

Note • In future releases, this behavior will be modified to append imported data instead of overriding existing data in an identical inventory item in the target project. Until then, exercise caution by exporting data from the target project before performing an import. In this way, you can recover the overridden data if necessary.

Manually Unreviewed Files

A codebase file that is manually “unreviewed” in the source project does not retain its unreviewed status in the target project if the target codebase scan has marked the corresponding target file as “reviewed”. This occurs because the data file to be imported stores information about only those codebase files that have been marked as reviewed in the source project. Hence, no information about the unreviewed file exists in the import data to overwrite information for this same file in the target project.

If, during a standard import, you want to retain the reviewed and unreviewed status of codebase files as defined in the source project, manually mark all of the codebase files in the target project as unreviewed before importing the data file.

Open topic with navigation