Seeing log entry: org.mozilla.javascript.EcmaError: "OR" is not defined.

Allen Andreas · ‎11-07-2019

Hi all,

I'm on New York Patch 1 Hotfix 1a and I'm seeing this in my system log (that is spammed about 50 times per occurrence):

org.mozilla.javascript.EcmaError: "OR" is not defined.
Caused by error in <refname> at line 1

==> 1: OR

Example:

So I understand what this says...but I'm unable to find where it's coming from.

From my own investigation...this seems to happen in list view (can't seem to replicate error on RITM list view, but see it on All Incidents list view and All stories list view) and then I go and check the logs and voila...it's spammed there.

This seems something like this issue:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0721365

Curious if anyone who has upgraded to New York (preferably the same version/patch I'm on) see this same evaluator warning in their syslog?

Also curious, without submitting an HI ticket...would anyone know how to even find WHAT is giving this evaluator log entry?

-Allen

Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Mwatkins · ‎11-13-2019

Based on the Jelly templates in your debug output we know it must be from one of those files. That combined with the fact that we know if must be a file that contains the term "OR" I was able to narrow this down to a particular line of code in the file list2_row.xml; which handles the rendering of list rows.

The line of code only executes if the glide.ui.list.detail_row property is set to true. When I set it to true in my demo I get the same errors in my logs. This seems to be a product defect that occurs when the property glide.ui.list.detail_row has been added to an instance and set to true.

https://docs.servicenow.com/bundle/newyork-platform-administration/page/administer/list-administrati...

The only way you could avoid these EcmaErrors is to disable that property but you would lose the functionality it grants. Please open an Case with ServiceNow support so they can create a Problem record for development to fix.

P.S. If you haven't already, remember to set glide.ui.template.trace to "false" as soon as possible since it creates excessive logging.

View solution in original post

Allen Andreas · ‎11-13-2019

Just wanted to confirm that a Case has been submitted to SN in regard to this issue with elaborate details and of course a link to this community post for them to review.

Thanks again for your assistance and I'll keep everyone else posted as this progresses.

Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Allen Andreas · ‎11-14-2019

Just wanted to give an update on this. I heard back from ServiceNow in regard to the case I submitted:

Investigation Summary:
Thanks, for reporting this issue with us. We acknowledge your effort in being proactive and providing us good information related to the issue.
I am able to reproduce this issue in the OOB New York instance with given steps to reproduce.

Next Steps:
I have raised PRB1373955 for our development team to check it further.
I will give you more update once receive information from them.
***

So they are aware, they can replicate, they are going to look in to.

Great news!

Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Allen Andreas · ‎12-18-2019

Just wanted to update once more, we now have a "known issue" article posting about this:

https://hi.service-now.com/kb_view.do?sys_kb_id=947046361b654c10a59033f2cd4bcb5c

Looks like it won't be fixed until Paris version, supposedly.

Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Allen Andreas · ‎03-10-2020

So I just wanted to finally come by here and mark the Correct answer. I was trying to wait until it was officially corrected in a ServiceNow release, but for those of you who are able to see the information in the hi article above, it's still projected to be fixed in Paris.

@Mwatkins has waited long enough for those +40 points for the Correct Answer, haha. Because at the end of the day...that was precisely what the problem was, so it is Correct all day long!

Thanks again! and we should see this resolved later this Fall!

Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!