adding variable set to catalog items creates a lot of warning

SHA3
Giga Expert

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

1 ACCEPTED SOLUTION

SHA3
Giga Expert

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

12 REPLIES 12

SHA3
Giga Expert







There is 1 other variable(s) with the same name associated with the variable set 'Business Justification', which is linked to the catalog item 'org.mozilla.javascript.Undefined@123ba32'



There is 4 other variable(s) with the same name associated with the catalog item 'org.mozilla.javascript.Undefined@123ba32'



These are the Warnings we are getting, there are too many entries .... like this which is resulting in catalog item not showing all variables or when update set is moved we find questions repeated or deleted.


Paula Cullen
Kilo Guru

We just upgraded from Berlin to Dublin and we're having the same issue with the variable set we put as a header on all of our catalog items. Looks like a business rule "Check for same name variables" was added to stop variables of the same name from being created. I have a ticket open with support to see what's going on.



Seems weird because the nature of a variable set is to allow the same variables to appear in multiple places.


same is true in order guides.. if you want a variable to be carried from the order guide to the item... you have to give it the exact same name.. what an odd warning.


gbernie
Kilo Expert

Hi Shilpa,


We are facing the same issue and we have Eureka Hotfix 5 installed.


We pretty much can't do anything. I have a HI ticket logged to see if Service Now can help.


If I try and add shared variables I get the errors displayed.


shared variable error.JPG


If I get any update I will let you know.


Regards.


Gareth