Import detail

Import provides functionality of pushing in data to Xeelo from the different sources.

Usage

The import can be found in Exports&Imports -> Imports section. In case of adding new import, it is necessary to specify the releated object. There are other parameters:

Parameters Description
Type Input data are in CSV file with UTF-8 or ANSI encoding
Restricted Works only if the request is in My Tasks
Create new The import will create a new request contains the data. It is necessary to choose the object template
Update The import will update a request which is already created. It is necessary to choose the update action
Only completed The import will be applied only on request in completed status
Update empty Erase the new request

Next step is to define the sections in Exports&Imports -> Imports. The sections are able to set in the content menu on each row. Click on the Red-wheel button -> Sections. In section It is possible to specify what type of element it will be imported (Request or Sub-Grid)

Note: If you import file, please take care of file encoding (UTF-8 etc)!

In case that the user is uploading import manually through the User environment, it is necessary to use same format like the data are exported (Import ID, RequestorID and NextUserID). Example below:

Updating of the Request

In case of the updating of the request it is important to follow the rules (Numbers in list mean Order in Import):

  1. ID (optional) - identificator - must be Unique for Object. For example: Employee Number in object Employee. This line specific the request that will be updated
  2. Sub-Grid ID (optional) - identificator - must be Unique for Object. For example: Contact Number in Sub-Grid Contacts in object Employee. This line specific the Sub-Grid line of the specific request that will be updated

Internal Import

Internal Import is following the rules right above.

  • In general - for every internal import (import section) there has to be also an internal export defined.
    • For example: There can be one import defined with 3 import sections. And each import section would then have 3 exports defined.
  • Internal import can be classified to 3 types
    • Import that will create a new request
    • Import that will update existing request
    • Import that will update existing request (in completed status) and make a new version of that request

Examples of 3 types of internal import

  1. Import from Request (Main grid) to another Request (Main grid)
  2. Import from Request (Sub-grid) or (Main grid + Sub-grid) to another Request (Main grid)
  3. Import from Request (Main grid) to another already existing Request with Sub-grid

1) Import from Request (Main grid) to another Request (Main grid)

This type of internal import is the easiest one.

  • First that needs to be done is creating a new import (import section) - Go to Admin/Import details and create a new import
    • Leave the Type as UTF-8
    • Select Object into which data will be imported
    • Select “Create new” and a template of an object under which the import will happen if you want to create a new request by the internal import. If you want to update the request select Update.
      • For update of a request and not making the Update (new version of a request) leave the section Update action empty.
      • To update a completed request and making a new version of a request, select an update action under which the update will be initiated and check “only completed”.

  • After above values are set, create a new import section which its ID is crucial for the internal import. (it is used on internal export afterwards)
    • Select type of import - whether data will be imported into Request (main grid) or Sub-grid. It is not possible to import data with one import to both types (Two imports have to be used).
    • Template override can be used if there are more than one import sections and the specific import should be done on a different template than it is set on Import.

  • Define lines that should be imported in section Lines, the first added Line position is set to value 1 as a default, subsequent lines are indexed incrementally.

  • Great! You have just completed defining import. Now to be able to use it, it has to be linked with Export. Go here Export to make the next step.

2) Import from Request (Sub-grid) or (Main grid + Sub-grid) to another Request (Main grid)

This type of import is more or less the same as the one above. Difference is that it will import as many requests as how many subgrid lines will be created in the request where export is defined.

3) Import from Request (Main grid) to another already existing Request with Sub-grid

This type of internal import is more complex.

  • First that needs to be done is to properly set the object with subgrid.
    • To be able to import from a Request (Main-grid) to existing Request with Sub-grid, unique lines (Object unique level) have to be set. One line that identifies the main grid and one line that identifies the Sub-Grid. (For the subgrid the unique attribute could be set only amongst the subgrid, so a calculation “Server-SubLineNumber” which assigns an order of subgrid lines can be used)
      • After unique attributes are set to object lines - these object lines are automatically assigned to an import.
  • Go to Admin/Import details and create a new import
    • Leave the Type as UTF-8
    • Select Object into which data will be imported
    • Select Update, no necessary to define Update action for this type of import.
    • After above values are set, create a new import section which its ID is crucial for the internal import. (it is used on internal export afterwards)
      • Select type of import - Sub-grid and specific Sub-grid.
      • Template override can be used if there are more than one import sections and the specific import should be done on a different template than it is set on Import.
    • Define lines that should be imported in section “Lines” - Lines that have the unique attribute set are automatically added with order “0”. Change the order of them.
  • Great! You have just completed defining import. Now to be able to use it, it has to be linked with Export. Go here Export to make the next step.

Export lines (subGrid)

Import lines (subGrid)