Working with Asset Records in TeamDynamix Asset applications

Overview

A step-by-step article describing adding asset and updating asset records in bulk. 

Importing with the Asset/CI Application Import Wizard

Users within an Assets/CIs Application can use the import wizard to import assets, contracts, product models, vendors, locations, location rooms and configuration items from an Excel file.

To import items using the wizard:

  1. In TDNext, go to the Assets/CIs Application and click the Import link on the toolbar.
  2. From the dropdown, select the type of import you’d like to do.
  3. A new window will open with instructions on how to run the import. Each of the import wizards offers the option to download a template file, which will include lookup values specific to the Asset/CI Application. Either use the template file or generate your own Excel import file, and select that file in the Upload field, then click the Next button. 
  4. Select the desired worksheet in the Excel file and specify if the file contains headers in the first row.
  5. Click the Next button. 
  6. Review the mappings between Source Column and Map To. If you used the template file, you should not need to change these options.
  7. Click the Next button. 
  8. Review the preview data and the number of rows that will be imported, then click Import and click the OK button to confirm. 
  9. Review the import results page, then click the Finish button or close the window. 

Gotchas & Pitfalls

  • It is common to struggle with knowing exactly what data needs pulled from a tool like SCCM. It is unlikely that all SCCM data would be pulled into TDX, so internal discussions are needed to sort this out.
  • It is important to import the data into sandbox first before taking the data to prod to make sure it is set up correctly.
  • If you run the previewer and data is being pulled back, but all of the rows are red, it is likely that something is malformed in your XML document. The most common cause is that your XML tags aren't cased correctly (e.g., you're using <NameMatchColumnID> instead of <NameMatchColumnId>).
Print Article