Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Gateway for 2D Data

Appendix F: Reserved Attributes Used in the Gateway

Appendix F: Reserved Attributes Used in the Gateway

  • Last UpdatedMar 24, 2025
  • 2 minute read

The following reserved attributes are used by the Gateway to apply and implement mapping. They should therefore not be present in the extracted source data, unless they are being used for this purpose.

  • ObjectId: It is used to map Id to the EIWM object. During the transformation phase, the Gateway creates "ObjectId" attribute or overwrites it, if already present.

  • ClassId: It is used to map Class Id to the EIWM object. During the transformation phase, the Gateway creates "ClassId" attribute or overwrites it, if already present.

  • ContextId: It is used to map Context to the EIWM object. During transformation phase, the Gateway creates "ContextId" attribute or overwrites it, if already present.

  • TemplateId: It is used to map Template Id in which the EIWM object is present. During the transformation phase, the Gateway creates "TemplateId" attribute or overwrites it, if already present.

  • IncidentalClassification: It is used to map IncidentalClassification association to EIWM object. During the transformation phase, the Gateway creates "IncidentalClassification" association or overwrites it, if already present.

If any of these attributes are present in the source data, then appropriate mapping should be configured to ensure that they do not have unintended effects. For example, if the source data has a "Revision" attribute, then mapping can be used to rename this attribute, for example, "Source_Revision". Otherwise, the EIWM loader interprets this to be the Revision value for the relevant object.

Reporting for Reserved Attributes in Extracted Data

Generate a CSV report of the extracted data to check if there are any reserved attributes present in the extracted data.

This CSV report should be generated before any other transformation processing. Insert the following transformation extension node before all other extensions, in the transformation configuration file.

<extension name="CSVReporting" >

<csvReport suffix="_BeforeTransformation" columns="ObjectId, ObjectName, ClassId, ContextId, Revision, TemplateId, IncidentalClassification" addHeaderRow="true" />

</extension>

This will generate a .csv file containing information about engineering objects that may contain these attributes. If there are any objects that have a value associated to any of the above attributes, it might cause unexpected results.

TitleResults for “How to create a CRG?”Also Available in