Date: Fri, 29 Mar 2024 04:38:47 -0700 (PDT) Message-ID: <1887883102.1091.1711712327845@ip-172-30-17-85.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1090_1412677264.1711712327826" ------=_Part_1090_1412677264.1711712327826 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Conditional field visibility improves the user experience by hiding irre= levant fields dynamically in the record form, depending on the options the = user selects. Visibility dependence can be based on one or more condit= ions that combine to determine whether the field is visible. Each condition= is based on a Choice or Multi-choice field having certain v= alues. You can choose whether to show the field if all conditions are = met or if any of the conditions is true.
You can set visibility dependence for a field:
Example
To meet this requirement, add the two conditions on the Options tab of t= he Field wizard and choose "Any of the conditions are met."
As with other field settings, System Admins or Table Admins can set visi= bility dependencies, provided their group has admin access to the tables co= ntaining the affected fields.
In order to see a visibility dependent field, users must have view permi= ssion for the dependent field itself. In addition:
Notes:
The graphic examples below show how different combinations of view permissions and true conditions<= /span> affect users=E2=80=99 ability to see a dependent field.
In addition to setting visibility dependence based on the value in a fie= ld, you can also configure visibility dependence so a field is only visible when a saved search finds a give= n record. This allows you to create more powerful conditions for visibility= dependence.
For example, maybe you want to make the Contract Not= es field visible only when the Contract Amount field is between $10,000 and= $50,000. To accomplish this, you can use a background table with a few fields, as well as a <= a href=3D"/display/HELP/Linked+Fields">linked field, an Update Fields action, and a saved search in the Contra= cts table, which together set a trigger field. The trigger field allows you= to determine the visibility of the Contract Notes field.
Let's see how you can configure the previous example by using the instru= ctions below. If you have a different use case, you can substitute your own= search condition, fields, and other items where relevant.
Begin by creating a background table to hold the record and the necessar= y fields. Two fields define the numeric range that the saved search will la= ter use, and a third field acts as the trigger field for the visibility dep= endence.
Next, create a Link to Selected Fields from Other Table in the Contract= s table that links to the ID and Show Contract Notes fi= elds in the Numeric Range table.
Now that the linked set is created, configure the be= havior for its default value. This is where you use an Update Fields action= and a saved search to find the record in the Numeric Range table, which se= ts the Show Contract Notes trigger field.
$contract.contract_amount
.<=
/li>
$contract.contract_amount
. Note that po=
inting to a Calculated Result field will not allow the default value to pop=
ulate instantly, and it will instead populate only when you save the record=
. When you're finished, the saved search should look like this:Next, create and configure the Contract Notes field to use visibility de= pendence.
Lastly, test that the visibility dependence works as intended.
If a user does not have permission to view any of the fields in a record= tab, the tab will automatically disappear from view. If the visibility con= ditions are satisfied for even one field in a tab, the tab will be visible = in the record layout. If the visibility conditions for any field are change= d so that the user can view it, the tab will automatically become visible f= or them.