adding variable set to catalog items creates a lot of warning

[SHA3]

Hi Experts,

We have created some variable sets which are used in multiple Catalog items. But these Variable set's variable are leading to a lot of Warnings.

Which says, the same variable is used in other catalog item. As of now we have created more than 30 catalog items. For adding each Variable set we have to kill the session after adding in slush bucket. The same happens even if we want to change the Order of the variable set in the catalog Item.

Now we are facing more issues as the number of catalog items using these variable set are increasing, we are now facing that the variable set is not visible at all in other words they are not attached well.

If anyone has faced the same issue, please let us know what could be the mistake from our end or how we can find a workaround or fix the issue.

Warning at Logs is:

org.mozilla.javascript.EcmaError: Cannot convert null to an object.
    Caused by error in <refname> at line 1

==>     1: parent.table

org.mozilla.javascript.EcmaError: Cannot convert null to an object.
    Caused by error in <refname> at line 1

==>     1: parent.variable_set

[SHA3]

Hi Donna,

I have used catalog items names short version in front of each variables prefix to distinguish it from say Variable set variables.

Cat Item: Access Card

Varibale set has variable : emp_id

In catalog item there is one more need to have a variable employee id, to keep it simple i would add "acrd_emp_id" to distinguish it from other variables.

This is a very simple example, hope this helps. There may be other better ways of doing this. Inputs/advises are appreciated.

[sarahisml]

Hi, I am new to ServiceNow. Can you explain more on how to do so ? thank you !

[SHA3 · Accepted solution]

This could be pretty late to reply on the solution. But i would add the findings anyway.

It was a business rule which was added by Service now which caused the issue. Later business rule was disabled and reported to service now, and later releases never faced such issue so the issue is resolved.