Mapping dependency fields.
Many a time, a picklist field’s values are so many that it gets difficult to find the right one when needed. A very common example would be that of the Country and State picklist fields. Imagine if you had an entire list of countries and also a full list of all the States to find and choose one. How tedious and confusing that would be! But that is not how we have it! We generally select a Country and the relevant State values are populated to choose from.
In a similar way, you can create dependencies between fields where there will be a parent field or the controlling picklist field and a child field or the dependent picklist field. The parent field would control the values that needs to be populated in the child field. For example, if you are selling 10 products, each having 10 models, a sales rep might waste time searching for the right product model from the big list. So instead, you can create two picklist fields - Product and Model. Based on the product selected, the Model field's values will be populated.
Another example: You have a service based business where you address various requirements of the customer. The services are packaged based on editions.
In this example, you can use the Edition Required as the parent field. Based on the value selected for this field, the Features Available (child field) field's values are listed.
This kind of relationship is established by mapping dependency fields in Zoho CRM. You can define which values will appear in the Child field when a certain value is chosen in the Parent field. For more information, refer to Mapping Dependency Fields.
For more information, refer to Map Dependency Fields