Removing a Parent-Child Labor Charge Value Association
As an administrator, you can unlink labor charge values that have been associated with other labor charge values in a parent-child relationship. The two labor charge values will continue to exist, unless they are completely unused and you also choose to delete them, but they will no longer be linked hierarchically.
To remove a parent-child association:
Click the Setup tab.
Under the Setup
tab, click Department.
A Department Values
page
opens and displays the specific
department codes that have been created.
On the Department Values page, click the link in the ID column for the parent value from which you would like to remove child values.
A Department page opens and displays the properties of the specific Department you selected. An informational message near the top of the page indicates that the labor charge field is part of a hierarchy and identifies the parent and child labor charge fields (for example, ”This Labor Charge Field is defined in a hierarchy. Project is the parent and Task is the child”).
On the Department page, click the name of the child labor charge field in the menu on the left side of the page. A table lists the child values, if any, that have already been associated with the parent value you selected.
Note:
If the menu is not visible, click the button to
show the menu. If neither the menu nor the button
is visible, the labor charge you have selected is not configured to
accept child labor charge values.
A hierarchy can have more than two levels. For example, Job could be
the parent of Project and Project could be the parent of Task. Only
one level of the hierarchy (that is, one parent and one child field)
can be viewed from the Labor Charge
page.
Click the check box to the left of each child labor charge value you want to disassociate from the parent value.
Tip: To select all of the child values, click the check box in the header row of the table.
Click the Delete button.
Note: This action does not delete the selected labor charge values from ezLaborManager, it only removes the parent-child relationship. Users will still be able to select and use these labor charge values, although they will now not have to first select a parent value.