The CreatorCon Call for Content is officially open! Get started here.

Make field visible when another field changes

BiancaK
Tera Expert

Hi Developers

I am trying to achieve the below. When a user changes the Forecasted date then the fields "Reason for change, Category and Sub category" should become visible on the form and mandatory. I was able to configure the requirement to make the field mandatory when user changes the Forecasted date. But how can I hide these fields from the form initially?

BiancaK_0-1722548381038.png

 

Please the code below:

function onChange(control, oldValue, newValue, isLoading, isTemplate) {  


  if (isLoading || newValue === '') {  


  if(g_form.isNewRecord() && newValue!=''){

g_form.setVisible('u_reason_for_change', false);
g_form.setMandatory('u_reason_for_change', false);


}
  return;  

  }  

  if(oldValue != newValue)  

  {  

  g_form.setValue('u_reason_for_change', true);
  g_form.setMandatory('u_reason_for_change', true);


  }  

  else  

  {  

  g_form.setVisible('u_reason_for_change', false);
  g_form.setMandatory('u_reason_for_change', false);


  }  


}  
1 ACCEPTED SOLUTION

@BiancaK Try writing a ui policy to hide all the field initially. Then update your if condition for above code share by me as 

if (oldValue != '' && oldValue != newValue)

 

…………………………………………..
Mark it helpful 👍and Accept Solution !! If this helps you to understand.

View solution in original post

15 REPLIES 15

Alex Rose
Tera Guru

I would hide them either using your code 

g_form.setVisible('u_reason_for_change', false);
g_form.setMandatory('u_reason_for_change', false);

in an onLoad client script, or in a UI Policy.

Thanks Alex, yes I  need to hide it as a first requirement and then second requirement is to make it visible only when the forecasted date changes. The forecasted date is not empty.

 

Sandeep Rajput
Tera Patron
Tera Patron

@BiancaK Please create a UI Policy with a condition which checks if Forecasted date is empty. In the UI Policy Action make the u_reason_for_change Mandatory false and Visble False.

Hi @Sandeep Rajput thank you. I had a UI policy but it is not working.

Here are the steps from the start.

1. On a new form the Forecasted date will be completed and the form is saved, so the Forecasted date will never be empty.

2. Then at a later stage the user decides to change this Forecasted date, at this time when they are attempting to change the Forecasted date the Reason for change field should only appear on the form and be mandatory to provide a reason why they want to change the Forecasted date.