Hide Requested For/Requested By Variable Set

[DeIvory Gordon]

Hello,

I was trying to hide the requested for/requested by variable set on a catalog item.  I erroneously thought that inactivating a variable set and hiding it was the same thing.  Per the screen shot below, I changed active to false.  I tried to make active true again and I got the message "The catalog item Location Closure request has 1 other variables with the same name associated with it.  keep the names of variables associated with a catalog item unique.  1. Do you know how I make the "requested-by" True again? 2. Do you know how I hide the requested for/requested by variable set? 

[Brian Lancaster · Accepted solution]

Did you create a requested_by variable on one of the associated catalog items? You can use a UI Policy with no conditions to always hide requested_by in the variable set UI Policy tab.

[Brian Lancaster · Accepted solution]

Did you create a requested_by variable on one of the associated catalog items? You can use a UI Policy with no conditions to always hide requested_by in the variable set UI Policy tab.

[Robbie · Accepted solution]

Hi @DeIvory Gordon,

To answer your questions directly:

1. Do you know how I make the "requested-by" True again? - A variable name should be unique within the context of a Catalog item. Check to see if you have another variable with the same name (Not to be confused with 'question'.). Simply rename one of the value and set to true. 

2. Do you know how I hide the requested for/requested by variable set? The best way to hide a variable (or variable set) is to leverage a UI Policy. 

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.

Thanks, Robbie

[Varkunal]

Hello,

I could see here same requested_by variable is already there in different variable set so that's why error message is shown.

1) If you change the backend name of variable and active it error message will not come.

2) As @Brian Lancaster says using UI policy you can achieve your requirement.

Thanks