Skip to main content

Managers EDBL

Reference for the Managers EDBL import in Encompass: bulk-load user-to-manager hierarchies up to 7 levels deep, with field definitions. Needs the EmployeeEdit permission; v22.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 22.01

Pre-Conditions

  • You must have the EmployeeEdit permission to use this routine.

  • User records must exist in the system for all managers being assigned.

  • The routine supports importing management relationships up to 7 levels deep.

Steps

The Managers EDBL routine establishes management hierarchies within your organization by creating relationships between users and their managers. The system supports up to 7 levels of management hierarchy.

When importing manager relationships, the routine:

  1. Looks up UserID values from the translation data (if provided)

  2. Associates each user with the appropriate managers at various levels

  3. Creates management relationship records in the database

  4. Updates the Users table to link users to their direct managers

You can import data that includes just the first management level or up to all 7 levels of the management hierarchy.

This routine will match existing management relationships where possible, and then either create new relationships or update existing ones depending on your selected import action.

Fields And Definitions

Primary Identifiers:

  • UserID - The internal system ID of the user whose management chain is being defined

  • UserID_Translation - External identifier for the user that can be translated to a system UserID

Manager Level 1 (Direct Manager):

  • TranslationManager1User - External identifier for the user's direct manager

  • Manager1UserID - System UserID of the user's direct manager

  • Manager1ID - Internal system ID for the management relationship

Manager Level 2:

  • TranslationManager2User - External identifier for the level 2 manager

  • Manager2UserID - System UserID of the level 2 manager

  • Manager2ID - Internal system ID for the level 2 management relationship

Manager Level 3-7:

  • Similar fields continue for management levels 3 through 7, with the naming pattern following the same structure

Best Practices

  • Import users before importing their management relationships.

  • Use TableTranslations to map external user identifiers to system UserIDs when working with data from external systems.

  • When possible, provide both the UserID and the manager's UserID in your import file rather than relying on translations.

  • Begin with a simple hierarchy (1-2 levels) before attempting to import complex multi-level management structures.

  • For each user, you only need to specify their direct manager. The system will automatically build the chain to higher-level managers.

  • You can update specific levels of management without affecting other levels.

  • When updating existing manager relationships, include the appropriate ManagerID values if available to ensure proper matching.

  • For new management relationships where you don't have the ManagerID, provide the UserID and the appropriate manager's UserID.

Did this answer your question?