Import Asset Data into TagNet
In order for TagNet to do its job it needs to have some understanding of the Objects that it is tracking. This could be Product, Item, Part, GTIN or Asset Data. This 'Object' data can be imported into TagNet’s Object repository using simple XLS or CSV flat files that is populated according to mapping standards provided below. This could be a 'one time' import or done on a recurring basis. Examples can be found in the following TagNet Server directory or downloaded here
The first two (2) rows of the sheet define column names as well as detailed database information displayed in the comments as you mouse over a each column heading as shown below:
This import facility supports the following scenarios:
1.Import Base Item and Asset Data together in a 1:1 relationship
2.Import Base Item information only
3.Import Asset definitions in a 2nd step (after Base Item definitions have been imported prior)
User Defined Attributes can be added (example rows highlighted in rose).
When importing new data, use the ADD Action code (see column 1), when updating existing data use the UPD action code. When deleting data using the DLT action code. An audit report is generated after each import attempt indicating detailed success and/or error conditions. As with any implementation, you should consult your TagNet Project Manager prior to using this feature.
Immaterial of an external system, the XLS import feature can also be used to speed up the entry of Asset Data into TagNet by using the cut and paste feature of Excel to generate data quickly and bypass the TagNet browser maintenance functions.
There are a number prerequisite steps than need to be performed as listed:
1. Creating a Data Import Binding profile
Ensure that the Data Import Binding is setup under Event Bindings
2. Executing the TagNet Import Job
Take the Import the TagNet Asset Data menu option that imports the data, validates and produces an audit file output. This method to import is typically done for infrequent imports or for first time initial loads to get experience. Once this becomes production ready use the schedule task feature below.
3. Check the results of Import log to verify
Check the Import audit file (CSV) in folder path D:\TagNet\rfid\import\Archive as shown below
Open the Import audit file (CSV) and review the log, an ERROR will be logged if an Asset ID or Base Item already exists in TagNet when attempting an ADD. Where an OK is shown this indicates the add of the given Asset ID or Base Item was successful. Make whatever corrections to the source Import XLS and resubmit the import.
4. Making the TagNet Import Job a Scheduled Task
Navigate to the Scheduled Task via below and follow the steps in the Scheduled Tasks topic that will import your data on a scheduled basis.
Copyright © 2022 Stratum Global, Inc.