adding variable set to catalog items creates a lot of warning

SHA3 · ‎09-12-2014

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 · ‎07-18-2017

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.

View solution in original post

randrews · ‎10-27-2014

if it is just a warning i am a little confused by why you cant' do anything...

we got those a LOT before we upgraded to Eureka when we added a ui action to a client policy and just continued and it worked fine...

after you add the variable set and test it and the conflicting items.. do they work as intended?

gbernie · ‎10-27-2014

Hi Doug,

It looks like I have some items in the Catalog, Service Catalog, and some with no catalog listed and this means I get the error and then it won't display on our cms.

gbernie · ‎10-29-2014

Service Now turned of the two business rules called ,'Check for same name variables'. This resolved my issues.

SHA3 · ‎10-31-2014

Hi Gareth,

We also turned off the Business Rule which has fixed the issue. Sorry i didnt reply soon.

dlively · ‎06-29-2017

Is it a good use case to use multiple variables with the same name or is there a better way to develop a service catalog?