FAQs in this section
What are dependent fields and blocks? Are dependent fields and blocks applicable everywhere in the CRM? What are the prerequisites to configure dependent fields and blocks? How do dependent fields and blocks work? How can I configure dependent fields and blocks? How can I edit an existing dependency? Why can't I see a field value in List View? What is block and field dependency? What are the different access rules? Will the dependent field appear in the same order defined in the module layout?
What are the limitations in dependent fields and blocks?
Table of Contents
Here are a few limitations that you must be aware of:
- A dependent field cannot be a controller (Trigger) field.
- If you move the Trigger field to a different block in the Detail View Layout after setting up a dependency rule, you must reset the rule associated with the Trigger field.
- When a Trigger field is disabled, the condition will be in a Strikeout mode.
- Dependent fields will slow the list views. If List View columns include dependent fields, then it could take more time to load the list.
Was this FAQ helpful?
0 out of 0 found this helpful.
Be the first to comment