The Data Import application allows to synchronize users and devices from different data sources - such as an Active Directory - so that this information does not have to be managed twice. The Data Import is a one-way-sync into the i-net HelpDesk server, meaning it does not write any modified data back into the data source. Data sources have to be set up in the Configuration Manager application.

A companies user data is usually managed in a central place, such as an Active Directory. This data can be imported into the i-net HelpDesk using the LDAP interface. If the data is managed in a different data source location, a connection can usually be set up to this.

Here is some more information on how the data to be imported is handled.

Device data can be manually managed in i-net HelpDesk, like in MS Access or MS Excel, but much more comfortable. In many companies there is already an inventory software solution which puts thousands of collected data records in a SQL-Database.

Typically you will only need some key information like name, serial number and purchase date in your ticket system. You can import such information in the i-net HelpDesk. With that you can maintain the data in ONE central place just as before and ensure the consistency of your data.

Here is some more information on how the data to be imported is handled.

The sets in the data source will most likely not match the structure used in the i-net HelpDesk, though an automatic matching for unambiguous fields will be suggested. Fields have to be matched manually. Fields that are not mapped into the i-net HelpDesk will not be modified when synchronizing the data. Empty values in the data source will clear the respective field.

The preview should be used to check that the expected data can be found. It shows up to six records.

The data import can be set up to be executed:

• manually: Recommended setting to test the overall functionality.
• planned: Automatically synchronizes the data using the configured interval. Jobs can be deactivated, for example when the datasource is temporarily not available, using the options menu.

The job overview lists all jobs that have been run in the last 24 hours.