Importing First Data

Almost every ClassiX module allows to upload master data with specially designed Excel files.

The module load macros are held in extra files to prevent the master modules from being overloaded with code. These modules have the same name as the master module, besides their file extension (.lod instead of .mod).

Extra files are not part of the standard project. If required, please contact ClassiX.

The directory should be structured as follows:

appswh\ [projektname] \load\*.lod

This file path has to be specified in CX_PATH in the START.bat.

Since the load macros are generalized, it is always necessary, to import the dfltrout.lod, too. It also gets included in the load directory.

 The following files are essential to import master data:

• module master lod file, which contains the import data  
• dfltrout.lod for the generalized load macros
• Excel file with master data to be imported

Excel import file name and path are always hard-wired in the master lod files of the macro "NameOfExcelFile". To import, the Excel file needs to be either renamed, or the file name has to be adjusted in the -lod.
 

The command "LoadObjects" in the module editing window starts the import.

Information:
In case neither the Excel file name, nor its file path shall be adjusted to the lod, it is also possible to write file name and path into the variable manualFile, before calling "LoadObjects". The load macro then uses this file instead of the hard-wired one in the lod. The load macro could look as follows:  "Y:\ClassiX\Evaluate\Kundendaten.xls" -> manualFile LoadObjects

File example - customer data:

Required files:

• customer.lod  (in load directory)
• dfltrout.lod       (in load directory)
• customer.xls   (in projects\data directory)

Excel file design and generalized macros

General:

Excel file name
Importing an Excel file, file name and path are always in the according .lod file in the macro NameOfExcelFile.

Excel file data design

• The first row indicates the column content. The system does not interpret this information, since it is optional and only for the users.
• The second row defines the program call for each row in the particular column. These InstantView commands and macro calls belong to the current module or  to the current .lod file, which has been created for import only.
  Information
  In case a particular program function is required for the import only, it has to be created in the .lod file.
• All following rows list the required import data.

Database Layer:
The Excel work sheet controls, where (in which database layer) to write the data. Work sheet 1 data (at the very left) is written into the first layer, work sheet 2 data into the second layer and so on.

Database Domains / Client Differentiation
There is another possibility to divide data inside the database layer - the domains. The lod file for general load macros (dfltrout.lod) provides a macro, which always sets the domain correctly, using 2 passed parameters - SetDomainByClass. The first parameter (Stack TOP) is expected to be the according class; the second parameter is expected to be the domain for reading and writing. 
2 CX_PARTNER SetDomainByClass would adjust the CX_PARTNER domain for reading and writing in the current layer to 2. Depending on the system data setting, this is the domain of the second client. Data that has been imported with this setting can be detected in the second client's partner mask only. 

Load Macro
The macro "InitEditObject" is called from the according .lod file after each imported row. The EditObject macro call provides a different amount of passed parameters in different modules. Therefore, it is important, to specify this ZERO EditObject statement per module with all required parameters in the lod. file.

The following examples show the principle of import interfaces:

• define domain: The first column lists the client. In this case, client 1 obtains a partner entry and client 2 another one. In case both clients shall have the same entries, although they are having separate partner, the files need to be copied and pasted with the other domain at the file end:

• enter name: In the next column, the InstantView command "PutValue" enters the cell content in the editing window. During import, this command has the same effect as the usually, manual value entry in the editing template.
• sales tax ID Nr: The next one works just like the column "enter name", but here the input field "vatID" is filled in the entry template.
• industry: In this column, a macro is accessed, which has been defined in the .lod file. The macro calculates the particular industry by the passed number and enters it into the template.
• phone: In this column, the phone number is also sent to a macro. This macro independently generates a new access object for the partner, in which it then saves the passed phone number.
• save: The entered mask data is being saved and a new partner gets generated. Since only those columns are executed, which do contain a value in the data rows, these data columns contain the value "NoOperation". Setting the control variable "TRUE -> executeEmptyCells", makes it possible to control the system to execute the empty columns before import anyways. 

This way, existent Excel files can be completed quickly by the according first two rows and their columns, and be directly imported.