adccommunitymod (AutomationDirect) asked a question.

Productivity Suite, More Flexible Tag Database Import

Created Date: August 24,2018

Created By: crashkopf

**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****

I know there's been a couple topics on this, but I thought I'd add my own particular requests. Tag importing is an amazingly useful tool, especially if you 're trying to do something like generate tags from an equipment list (e.g. exported sheets from Plant3D). A couple extra features would remove some friction points in this kind of workflow. Make the columns re-orderable. Right now the import feature requires columns to be in a particular order. Either pull the column name from a header row or let the user define column order as part of the import workflow. Only require certain columns, like tag name and data type. Columns for which a suitable default can be generated should be optional. Make import errors more explicit. If a needed column is missing or the data in a cell is not of the correct format then describe the exact row and column location and type of failure. Right now I just get a line number and "Unknown or missing data type. " Thanks.


  • adccommunitymod (AutomationDirect)

    Created Date: August 24,2018

    Created by: crashkopf

    I know there's been a couple topics on this, but I thought I'd add my own particular requests.

    Tag importing is an amazingly useful tool, especially if you 're trying to do something like generate tags from an equipment list (e.g. exported sheets from Plant3D). A couple extra features would remove some friction points in this kind of workflow.

    Make the columns re-orderable. Right now the import feature requires columns to be in a particular order. Either pull the column name from a header row or let the user define column order as part of the import workflow.

    Only require certain columns, like tag name and data type. Columns for which a suitable default can be generated should be optional.

    Make import errors more explicit. If a needed column is missing or the data in a cell is not of the correct format then describe the exact row and column location and type of failure. Right now I just get a line number and "Unknown or missing data type. "

    Thanks.

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: August 29,2018

    Created by: ADC_CommTeam02

    "Make the columns re-orderable. Right now the import feature requires columns to be in a particular order. Either pull the column name from a header row or let the user define column order as part of the import workflow. "

    Response: We will add this to our review of list of improvements .

    "Only require certain columns, like tag name and data type. Columns for which a suitable default can be generated should be optional. "

    Response: Since version 3.0.0.31 the only fields required are the tag name and data type. System ID is no longer a requirement.

    "Make import errors more explicit. If a needed column is missing or the data in a cell is not of the correct format then describe the exact row and column location and type of failure. Right now I just get a line number and "Unknown or missing data type. "

    Response: Agreed. We already have this added to our list of improvements.

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: August 29,2018

    Created by: crashkopf

    Excellent! Thanks!