Import a gateway model configuration

NOTE:
The Import feature will be available in the future release of FactoryTalk Edge Gateway distributed.
To reduce the time required for mass configuration, import the exported and edited gateway model configurations. Due to case sensitivity, the names in the CSV file must match the names in
FactoryTalk Edge Gateway
.
Tag bindings are case sensitive. Changing the case of tag bindings in the exported model CSV file and then importing the model CSV file causes an error. To ensure that the tag bindings are correct, copy and then paste the tag bindings from the exported data source CSV file.
FactoryTalk Edge Gateway
saves information about the validation of the model including errors and warnings in a log file in the
FactoryTalk Edge Gateway
installation folder under
FactoryTalk Edge Gateway\fteg-ct\export_import_logs
.
TIP:
It is not possible to import or export
FactoryTalk Smart Object
models. Build
FactoryTalk Smart Object
models in
Studio 5000 Smart Object Configurator
and then bring them into
FactoryTalk Edge Gateway
by using an ACD file.
To import a gateway model configuration
  1. Do one of these actions:
    • Preselect models and then select
      Import models
      ImportGatewayConfiguration_icon.
    • Select models in the dialog.
  2. In
    Select folder that contains configuration files
    , select the folder that contains the CSV configuration files to import.
    The models appear based on the model hierarchy specified in the CSV file. You can see the tags bound to properties if tags are bound to the properties in the CSV file.
    TIP:
    If the CSV file is missing required fields for a model element, then that model element does not appear in the preview. If a node is missing required fields, then the node and its children do not appear in the preview.
  3. Select the models to import.
  4. (optional) Before importing the models, select
    Validate
    to get the list of errors and warnings.
    The model name and its components that contain the error are listed.
    TIP:
    Models, nodes, or properties with errors are not imported.
  5. (optional) If a validation error occurs, modify the CSV file, validate the model configuration, and then import the model configuration again.
  6. Select
    Import
    .
    A new namespace ID is generated for new items in the model. If a node or property is renamed, a new ID is generated.
    TIP:
    If a model exists in the namespace and the CSV file has the same model, the existing model is overwritten during the import.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal