Using External Applications

This chapter describes how to export Kanban information to data files that can be used by external applications, as well as how to return modified data to the system.

Exchanging Workbench Data
Introduces the concept of exchanging data.

Kanban Workbenches
Describes how to import and export files and lists associated file definitions.

Supermarket Workbench
Describes how to import and export files which allow Supermarket Workbench (17.2.7) to be used.

Level Mix Workbench
Describes how to import and export files which allow Level Mix Workbench (17.14.1) to be used.

As an alternative to the three workbench programs available through the QAD .NET user interface, the system includes tools for exporting Kanban data to a comma-delimited file. You can then load the records into your specialized application such as a spreadsheet, manipulate data as needed, and import modified records back to the database. Based on the changes you make, the system automatically updates loop and process data.

Optionally, you can have the system reconcile loops based on modified data, inactivating or adding cards as needed. You also can create new kanban loop records, as well as other database records needed to support them, based on an imported file.

This chapter describes the export and import programs used to exchange Kanban data between the internal application and an external application, as well as the record structures of the files used as the interface between the two systems.

Important: A critical element of all three export/import procedures is an internal key created by the system in the kanban master table (knb_mstr). The Kanban Loop ID field (knb_primary_key) uniquely defines each loop in the system. This field cannot be viewed or updated through the user interface. This has the following implications on manipulating records with an external application:

• When you use Kanban Workbench Import, the system uses this ID to determine whether you are updating an existing loop or creating a new one. When an imported record does not include a value in the field, the import process attempts to create a new loop.

• With that exception, all records imported back to the system must contain the valid loop ID that was included in the export file.

The following sections describe how to export and import files so that you can use an external application to perform the same functions as the following QAD .NET UI programs: