Skip to main content

Hierarchical Lookup Maintenance Import - Overview

This import is a semi-fixed header import that will maintain data in these two tables: HIERARCHICAL_LOOKUP_GROUP HIERARCHICAL_LOOKUP_GROUP_ENTRY The import format is CSV.  The very first row of the im

Updated over 2 weeks ago

This import is a semi-fixed header import that will maintain data in these two tables:

HIERARCHICAL_LOOKUP_GROUP

HIERARCHICAL_LOOKUP_GROUP_ENTRY

The import format is CSV. The very first row of the import is the header row, and subsequent rows are data rows. The columns must be laid out in the order defined by the import (it is not flexible in that respect). All the columns are required. But, exactly TWO columns can accept one of two different header values, to indicate the type of data that the column will accept. Those details are given below.

The import can be run at the system level, or at the company level. There is no

COMPANY_ID field in this import spec, so the only way to deal with company level groups is to run the import at the company level.

The CLIENT_CODE field, when used, is unique PER COMPANY. System-level groups are treated as if they are all implicitly part of one company.

Here is the text that should go in each column of the header row, from left to right:

COMMAND

GROUP_NAME

REPLACEMENT_GROUP_NAME

PARENT_GROUP_NAME

GROUP_INACTIVE

ENTRY_ID --OR-- ENTRY_CLIENT_CODE

REPLACEMENT_ENTRY_CLIENT_CODE

ENTRY_DISPLAY_VALUE

PARENT_ENTRY_ID --OR-- PARENT_ENTRY_CLIENT_CODE

ENTRY_SEQUENCE

ENTRY_INACTIVE

Did this answer your question?