When adding Two Variable sets to a Catalog Item, one is not been added to the Catalog Item.

[Martijn Olthuis]

Hello,

We have the following business rule, Check for same name variables.

When we add two Variable Sets to a Catalog Item, we will get an error.  And one of the Variable Sets will not be added to the Catalog Item.

In the Variable Sets there are two Variables, with the same Name, One is Active, and the other one is inactive.

The Variable Set that has the inactive Variable u_original_requester will not be added to the Catalog Item.

Do you have any idea how to solve this?

Thanks,

Martijn

[Ankur Bawiskar]

Hi,

So what is the question?

If this is working as expected then what is the new requirement?

Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur

[Mark Roethof · Accepted solution]

Hi there,

The pictures appear really small here, too giving it a try:

In theory, try to work with unique Variables names when working with a combination of Catalog Items, Variable Sets, Multi-Row Variable Sets. In theory when having a combination of these three, having duplicate Variable names could cause a lot of issues with Visibility, Catalog UI Policies, Multi-Row Variable Set not being displayed, etc., etc..

Whilst I understand that some of your Variables are active=false, also for those to try to avoid duplicates Variables names. It's not recommended to delete the Variable (if your Catalog Item is already in production because deleting will also delete data!), though you might be able to rename the Variable.

Does this give you enough insight? Or do you need more assistance with this?

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

[Martijn Olthuis]

Thanks Mark, you mean bij  though" you might be able to rename the Variable" , I have to rename the Variable Name?

[Mark Roethof]

Yes I would rename the active=false Variable.
Again, just to be sure: if this Variable is already in production, don't delete! You might end up with losing data that way.

Though, I can't see from your screenshot if this is a Catalog Item or a Record Producer (where the Variable might have map to field=true). If the Variable has map to field, the name has been set through out-of-the-box ServiceNow artifacts (and maybe because of that the u_ name? when working with Variables you don't really need the u_, though if it's map to field you don't have this choice ofcourse).

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list