Hi @JGuerrero0323 ,

I think you have a similar requirement as mentioned in this.

https://www.servicenow.com/community/developer-forum/multi-row-variable-set-client-script-to-do-some...

Hi @JGuerrero0323 

• Create the Catalog Client Script:

  • Go to your catalog item.
  • In the Catalog Item record, scroll down to the Catalog Client Scripts related list and click on New.
  • Select Type: onChange.
  • Choose the Variable for the Yes/No question (e.g., "Required Accessories").

• Write the Script: Here's a sample script that should do the trick:

   

   

  function onChange(control, oldValue, newValue, isLoading) {
  if (isLoading) {
  return;
  }

  // Get the "Required by Date" variable
  var requiredByDate = g_form.getControl('required_by_date');

  // Check if the "Required Accessories" Yes/No variable is YES
  if (newValue == 'true') { // 'true' for Yes
  g_form.setVisible('required_by_date', true); // Show the date
  g_form.setMandatory('required_by_date', true); // Make it mandatory
  } else {
  g_form.setVisible('required_by_date', false); // Hide the date
  g_form.setMandatory('required_by_date', false); // Make it optional
  }
  }

If the above information helps you, Kindly mark it as Helpful and Accept the solution.
Regards,

Sachi Pai

@JGuerrero0323 

you have MRVS and based on MRVS variable value outside variable needs to be shown/hidden.

So it's not straight forward.

But what if user adds multiple rows 1 with yes and other with no?

what will happen in that case?

I suggest to add that Date variable within MRVS so that it makes more meaning to the users and they can specify for each row when they require.

Once this is done you can use catalog UI policy which applies on MRVS and on that Yes/No variable and show/hide the other date variable and make it mandatory

If my response helped please mark it correct and close the thread so that it benefits future readers.

Hi Ankur.
If the required_by_date variable is added inside the MRVS as you propose, each row will have its own date selection. However, the goal is to have a single required_by_date for all items, not separate dates for each row.

Since the requirement is to control the visibility of required_by_date based on at least one "Yes" in the MRVS, keeping it outside ensures consistency and avoids users selecting different dates for different rows