Question

The fields that are modified using the conditional layout, do they act in the modified manner in custom buttons as well?

Answer

Yes, the fields that are modifiied using the conditional layout keeps their modification when used in custom button

For example

User have configured a conditional layout that hides a Cpicklist field when lead source is cold call Also user has designed a custom button that shows the name of the contact and Cpicklist

Also user has configured a custom button that shows the Cpicklist in it

So, when user will turn the lead source to cold call, it will hide the Cpicklist. Will it also hide Cpicklist in the custom button?

Yes, it will also hide the Cpicklist in custom button

Problem

Conditional layout fails to execute and do not show the desired output

Explanation

A major reason behind conditional layout not working is that the user is using a checkbox field to trigger the workflow. It does not happen all the time but can cause problem in some specific instances

Checkbox commonly cause trouble when used in any of the automated/workflow processes

Problem

If a user use a related module field, to trigger a conditional layout, the conditional layout will not trigger

For example, if a user want to set a conditional layout in contact module, if the field "Organization type" is "Press" (in organization module) then hide the "do not call" field in the contact module

Then

Explanation

Conditional layout works with in a module. Means the field of a module can only be made mandatory, hidden & read only using the conditional layout, if the triggering field also belong to the same module. Although it shows the field from the related module as well to trigger the conditional layout, but they cannot be used to execute the conditional layout