1. Using Connect Client
  2. Hierarchical Trees

Hierarchical Trees

Net Change must apply a set of special processing rules to entities that are part of a hierarchical tree. For example, before deleting a parent node, all of its children must have been deleted. Net Change recreates the entire hierarchical tree to correctly sequence the order of operations required to synchronize the target application.

Hierarchical Entities:

  • Department

  • Employee

  • JobField

  • Location

  • Organization

There are two modes for hierarchical entities, full and partial. The full mode allows only a single root element, while the partial mode allows multiple root elements. By default the mode is full for hierarchical entities. The Employee entity can be full or partial.

The customer input CSV file must contain the entire data set of the hierarchical tree. The first line of the CSV file must be the root element, and will have no parent. In the Parent column, make sure “Skip column if value is empty” is checked. For partial mode, the root elements must precede their children in the CSV file. See partial example below.

Full

"Code(Child)","Parent,Code","Description",... 
"-1",,"Organization",... 
"DIV-A","-1","Division A",... 
"DIV-B","-1","Division B",... 
"T1","DIV-A","Team 1",... 
"T2","DIV-A","Team 2",... 
"T3","DIV-B","Team 3",...
Partial

"Code(Child)","Parent,Code","Description",... 
"-1",,"Boss",... 
"MNG-A","-1","Manager A",... 
"E1","MNG-A","Employee 1",... 
"E2","MNG-A","Employee 2",... 
"MNG-B",,"Manager B",... 
"E3","MNG-B","Employee 3",...

Errors

Hierarchical entities must be handled properly to prevent errors. The three main causes that generate errors using Net Change with hierarchical entities (HE) are:

  1. Using a parent relation that doesn't exist.

    Each time you create an HE that refers to a parent that doesn't exist in Monarch, you will get this kind of error.

    Monarch Functional Error: The parent node associated to this key has not been found: …

  2. Working with a partial “tree”.

    Each time you create an HE that refers to a parent that doesn't exist in partial “tree” but exists in Monarch, you will get this kind of error.

    Monarch Functional Error: The parent node associated to this key has not been found: …

  3. Transactions done directly in the Monarch application.

    1. We can generate an invalid structure in “Net Change database ” and destroy the “Net Change process” when we are doing modification in the UI of Monarch (Element in Green) while doing Net Change with TCC.

      If we do a “Net Change Setup” action using an existing element ( in Monarch, Element J) that is not directly linked to an element of the partial “tree” (used in “Net Change”), the “tree” is not valid anymore.

    2. If we do a “Net Change Setup” action using an existing element (in Monarch, Element E) that is directly link to an element of the partial “tree” (used in the “Net Change”), the “tree” is valid and it's possible to do Net Change if we do a “Setup” first and then a “Computation”.


Image showing a hierarchical entity.

Examples:

  • Case-1: Do Net Change Computation only (Move “Element J” under “Element B”).

    Monarch Functional Error: …You cannot update the following field: BaseComposite.Parent.

    Note that the field value and the supplied value don't match (as described in 3-a).

  • Case-2: Do Net Change Setup & Computation (Move “Element J” under “Element B”).

    • Setup runs with success.

    • Computation TCC WorkFlow Error: The parent node associated to this key has not been found …. (as described in 3-a).

  • Case-3: Do Net Change Computation only (Move “Element E” under “Element B”).

    Monarch Functional Error: …You cannot update the following field: BaseComposite.Parent.

    Note that the field value and the supplied value don't match (as described on 3-b).

  • Case-4: Do Net Change Setup & Computation (Move “Element E” under “Element B”).

    • Setup runs with success.

    • Computation runs with success (as described on 3-b).

The Partial hierarchical entity “Employee” is not impacted by the behavior described above. When doing Net Change with an Employee, you can get an empty parent or a parent that is not present in your Net Change Database.

We recommend that you always work with a full structure and respect the “Primary/Secondar” concept when doing your Net Change otherwise you can end up with a Employee structure that does not represent your company.