Script include working in Dev but when deployed to Test instance it wasn't functioning as expected

[Fredy Voke]

Hi All,

I would please need an assistance should anyone has an idea on how to fix my issues.

I wrote a script include which is to auto-populate a variable set values for existing RITM made within a month, and it worked in Dev instance but when update set was deployed to Test instance it did not work as it did in Dev.

I have checked and compared both scripted in dev and test instances the implementations were both the same, and I am not sure why its not working in Test instance but it is functioning in dev.

Both instances are in same Tokyo version and I am not sure why or what the issue is, kindly assist, Thanks

[Gangadhar Ravi]

@Fredy Voke please provide more info or share script include and where are you calling this from?

[Fredy Voke]

Find attached copy of the script Include, client script, variable set, and the portal behaviors in Dev and Test instances

[Fredy Voke]

Many thanks Ravi, hopefully my information will help in seeking solutions to my issue.

[Stefan Reichelt]

Can you maybe take a screenshot of the whole script windows, so we can see the parameters around? There may be other pitfalls such as cross-scope issues, the "isolate script" checkbox, and maybe others. Not sure if it's intended, but I can only see the same script twice. The Client Script picture seems to be missing.

Did you also check the logs?

PS: Regarding the GlideRecord - if you've got the sys_id already, I would personally rather work with .get().