Using a single entity for hierarchical filtering
Suppose we have a table of hierarchial data called Service Group. There are three levels of Service Group: SG1, SG2, and SG3. When a User selects Service Group 1, the options for Service Group 2 must be filtered based on the User selection. The same logic applies to Service Group 3.
We can configure this scenario using a single Custom Entity and self-referential relationships.
Step 1: Create Custom Entity.
I will create a custom entity called Service Group.
Step 2: Create self-referential relationship.
We will need to create a self-referential relationship for Service Group. To do so, create an N:1 referential relationship. The ID for this field will be the “Parent” Service Group.
Step 3: Create relationship with desired entity
Now, we need to create a relationship for each field on the entity (I will use Case) we desire to place the fields. Suppose I want to place these Service Group fields on the Contact. I will need to make 3 1:N relationships for the 3 Look-up fields.
The following settings will be used to Service Group 1, Service Group 2, and Service Group 3:
Step 4: Create views
Create view for Parent
Now we need to configure the Lookup Views. For the first field, Service Group 1, we want to create a filtered view so we don’t see the entire list of Service Groups. We only want to see options for Service Group 1.
Create view for Child
For Service Group 2 and 3, we don’t need to use a filtered view, as these will be filtered using filtered lookups.
Tip: Remove the “Created On” date field that shows up on the Lookup View to free up space in the Lookup.
Step 5: Add to form
Since the data will be hierarchically filtered, we will use filtered lookups on Service Group 2 and Service Group 3 to handle this. To do this, first add the fields to the form. Next, we will select the field and click Change Properties.
For the Service Group 1, we have to set the view to the one we created without a parent:
Since Service Group 2 and Service Group 3 are filtered based on the previous group’s selection, we will need to configure the filtering settings on the lookup to filter based on the previous group, e.g. Service Group 2 is based on Service Group 1 and Service Group 3 is based on Service Group 2.
Step 6: Test data
Now let’s test our hierarchical filtering! Let’s create three records to represent Service Group 1, Service Group 2, and Service Group 3.
Now, when we go back to the Case form and see the options for each look-up, the logic should be based on the selection of the previous Service Group, excluding Service Group 1.
Step 7: Import data
When we import the Service Group data, we simply need a table with two columns - one for the name of the Service Group, and another for the name of the Parent Service Group:
|Service Group||Parent Service Group|