Data lists in NLF format - SmartPlant Foundation - IM Update 48 - 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)

In addition to being able to create and update objects using the class definition or relationship definition name, NLF supports a third object format: data list definitions. The advantage of this format is that the user does not need to specify relationship definitions, and the code works out associated UIDs and determines whether these need to be terminated or not. This format is particularly useful for submitting list data such as Excel import data in which a view and data list definition have been defined.

.XLS_Tags

..DataListItem|5

..RelatedDocumentName|XLS_Tag_Data|DEVRelatedTag

..Tag_Name|CW811

..Tag_Desc|NLF Tag Create

..Tag_Category|Process equipment

..Tag_Type|Process vessel

..Overall_Height|10|m

..Overall_Width|7.6|m

..Overall_Length|8.2|m

..System_Name|10

..Document_Name|DocABCDE

.XLS_Tags

..DataListItem|6

..RelatedDocumentName|XLS_Tag_Data|DEVRelatedTag

..Tag_Name|CW812

..Tag_Desc|NLF Tag Create

..Tag_Category|Process equipment

..Tag_Type|Process vessel

..Overall_Height|6.78|m

..Overall_Width|4.6|m

..Overall_Length|5.2|m

..System_Name|10

..Document_Name|DocABCDE

Format

Description

.DataList_Name

Defines the name of a data list item.

..TargetViewDef|NameOfViewdef

If the data list supports multiple view definitions, then the Target View definition must be named in order for the property display values to match up with the correct view definition. If only one view definition is associated with the data list definition, then there is no need to specify this field.

..DataListItem|Value

This is a special keyword used with the NLF data list type in order for a compare operation to detect which data line was used to submit the data. The field is for reference only and never ends up in the database, but, it is returned as a reference in any compare results that are returned.

..RelatedDocumentName|DocumentName|RelDef

This is a special keyword used within NLF in order for relationships between the named document and all objects (those with a target class definition) to be established.

The code assumes that the attached document is on side 1.

..PropertyDisplayName|Value

Defines the property display name within the associated view definition.

If the property display name has spaces in it, then these need to be replaced with the underscore "_" character. The value (including the UOM if it is present) should follow.