Job summary import and export counts - SmartPlant Foundation - IM Update 48 - Help - Hexagon

Import counts

These are determined on import as follows:

• One object on multiple lines in one file is counted only once where the values for the properties are the same. However, if the same data is included in two different input files, it will be counted twice. This rule is in place to support the tracking of the data back to its source (file and line number) for error reporting.

• Blank cells for a property will still create the property but define no value for it.

• Blank cells for an object are ignored, assuming it is not mandatory. The object is not generated, the relationship is not created, and nothing is added to the counts. If the object is mandatory and has blank cells, the object is not created and an error is recorded in the validation report.

• The action defined on an item has no effect on whether an item is included in the import count, as everything is imported. This is unlike the export count, which is selectively based on the defined action.

• Constants are counted like a property on each applicable object, as per the mapping. For example, if a constant is defined for each tag and 1000 tags are created, the count will include 1000 properties for adding the constants, unless multiple lines reference the same tag.

Export counts

These are determined on export as follows:

• Information sent to the landing tables is dependent on the export map. If an object is not configured to be exported, it will not be sent.

• The export filter prevents objects with errors of a certain severity or greater from being exported.

• The action set for the item determines whether it is included in the export and the export count.

  • NoAction - The objects are not sent during export and they are not counted.

  • CheckExists - The object is not exported, but the relationship is sent. The object is counted.

  • Delete and Terminate - The object UID is sent, but not the properties. The object is counted.

  • CompareValue, CheckStagingFileExists, and CheckTargetSystemFileExists - The object's properties are not sent and the object is not counted.

• Relationships with an export action are sent to the target system, unless:

  • An object on one end of the relationship fails a CheckExists check.

  • An object on one end of the relationship does not pass the export filter.

  If either of this issues exist, the relationship is not sent and the object is not counted.

• Objects, properties, and relationships are included in the count if they are processed, even if no update was made to the item.

• Extra items may be created that are not included in the count. For example, additional relationships and other objects created due to claiming, and an export of a Primary Classification relationship will cause SmartPlant Foundation to fill in all relevant SPFClassificationLevel relationships.

• Implicit delete counts can vary between the summary and the actual implicit delete report generation. For more information on why this can vary, see Summary shows a different number of implicit deleted objects.