Exporting multiple revisions - SmartPlant Foundation - IM Update 46 - Help - Hexagon

SmartPlant Foundation Help

Language
English
Product
SmartPlant Foundation
Search by Category
Help
SmartPlant Foundation / SDx Version
10
SmartPlant Markup Plus Version
10.0 (2019)
Smart Review Version
2020 (15.0)

When exporting multiple revisions of the same document, the SmartPlant Foundation target adapter revises any existing revisions to create the latest revision from the CSV file. It then inserts any other revisions as historic revisions.

This behavior is different to revising a document incrementally in separate loads or loading multiple revisions in one load.

If the relationship copy behavior is defined so that the system copies the relationships on a revise, a relationship instantiated on Rev 1A, which is already in the database, is copied to Rev 2A, even if the relationship is not supplied in the CSV file. For more information on using revise, see Revisions and versions.

Example 1

The existing data starts as follows:

The CSV file is laid out as follows:

DocNumber

MajorRev

Minor Rev

Tag

Doc 001

2

a

As the existing revision has a relationship to the tag, the copy relationships ensure that new revisions have a relationship to the same tag.

Example 2

Alternatively, if two revisions are given in the CSV file working from the original starting data in the first example:

DocNumber

MajorRev

Minor Rev

Tag

Doc 001

2

a

P101

Doc 001

3

a

Both new revisions are related to the original tag (P100), because the system copies relationships from the existing revision. However, only revision 2 is related to the new tag (P101), because that relationship was explicitly created in the load file for revision 2, but not for revision 3.

Data Validator expects the relationship to be specified on every revision to which it is applicable. This behavior is consistent with interactively revising and then inserting historic revisions.