Edit assets of an asset node

Edit properties of assets under an asset node in the asset tree. To do so, you need to complete the following operations:
  • Create a CSV file with assets and editable properties as an import file.
  • Edit asset properties in the CSV file.
  • Import the CSV file with customized properties.
Prerequisites
  • Make sure no other user in the system is in Design mode before importing the CSV file.
To edit assets of an asset node
  1. In the
    Welcome
    dialog, click
    Next
    .
  2. In the
    Select an option
     dialog, select
    Edit assets of an asset node
    , and then click
    Next
    .
  3. Create a CSV file with assets and editable properties as an import file.
    1. In the
      Select an option for asset edit
      dialog, select
      Create import file
      , and then click
      Next
      .
      TIP:
      If you have already created a CSV import file, go to Step 5.
    2. In the asset view of the
      Export assets to edit
       dialog, select a node in the asset tree under which the assets you want to edit.
      TIP:
      If a device asset is selected, its parent container becomes the node. All assets under this node will be exported to the CSV file. If the device asset doesn't belong to any container, the root of asset tree becomes the node. All assets in the asset tree will be exported to the CSV file.
    3. In the
      File Saving Information
       field, specify the file name and file path to save the CSV file, and then click
      Start
      .
    4. (optional) In the
      Finished
      dialog, click
      Save Summary
      to save the result summary as a TXT file.
    5. To continue the importing process, click
      Back
       to return to the
      Select an option
       dialog. If you want to exit, click
      Finish
      .
  4. Edit asset properties in the CSV file.
    1. Locate and open the CSV file on your computer, and edit the asset properties, except for
      ID
      ,
      Type
      , and
      Path
      . Use unique names for each asset of the same type in the CSV file. If the CSV file includes multiple assets of the same type and name, only the first asset in the list can have its properties updated in the asset tree after the CSV file is imported.
      IMPORTANT:
      • Do not modify the information in the
        ID
        ,
        Type
        ,
        or
        Path
        column. Assets with the
        ID
        ,
        Type
        , or
        Path
        property modified cannot have their properties updated in the asset tree after the CSV file is imported. A CSV file with any column removed cannot be imported.
      • To import an extended property, don't just enter the property value while leaving the property name empty in the CSV file. Such extended properties will be skipped during the import. The default extended properties configured by the
        Options dialog box: Extended Properties
         do not affect the configuration in the CSV file.
    2. Save and close the file.
  5. Import the CSV file with customized properties.
    1. Return to the
      Select an option
       dialog, select
      Edit assets of an asset node
      , and then click
      Next
      .
    2. In the
      Select an option for asset edit
      dialog, select
      Import
      , and then click
      Next
      .
    3. In the
      Import assets to edit
      dialog, click
      Browse
      to select the CSV import file you have created and edited.
    4. Click
      Start
      . A progress bar shows as the tool updates the asset properties.
      TIP:
      Click
      Cancel
      if you want to cancel the current operation. Clicking
      Cancel
      does not undo asset property updates that have completed. You need to undo the property updates manually.
    5. (optional) In the
      Finished
      dialog, click
      Save Summary
      to save the result summary as a TXT file.
  6. Click
    Finish
    to exit the or
    Back
    to return to the
    Select an option
     dialog.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal