Hi Robert. ‘depChanged’ is actually ServiceNow code, but they’re refactoring their reporting interface starting in Eureka and very drastically in Fuji. As such, it looks like it is no longer available. I recommend you start using the standard ACL-based approach that ServiceNow has come out with since this capability was created here.

http://wiki.servicenow.com/index.php?title=Administering_Reports#Restricting_Report_Creation_with_ACL_Rules

We are having the same issue since upgrading from Calgary to Eureka (Patch 7). Support has given us the same response. Here’s what we got back from Support:

I narrowed the issue down to line 74 in the ui script (RemoveReportOptions), where a method called ‘depChanged()’ is being used. Something in that method is causing the issue.

I haven’t been able to figure out what this is doing exactly and can’t find a reference to this method anywhere else in the system.

I am also having an issue with this when we upgraded from Calgary to Eureka Patch 7.
Seems that on reports with a sort by it doubles the sort by when the report is displayed. Then if the report is saved, when the screen is displayed again and the sort by section is doubled again. So very quickly the sort by section can get very long.
Created a HI tickets and response was PRB608744, but then they came back that the developers had looked and that it was due to unsupported customization.
If UI Script RemoveReportOptions is made inactive then everything works fine, other than the list of tables is very long.
Trying to work out what in RemoveReportOptions is making the report screen double the sort by option on the screen.

I’m not positive, but I would make sure the UI 14 plugin is active in your upgraded instance. Outside of that, the only thing I can suggest is to check the console log in your browser and see if there are any error messages that could point you in the right direction.

Seems to work great in a fresh Eureka. But after upgrading from Calgary to EUREKA it has stopped working. Unsure why, or where to validate since the code appears to be the same?

Hey Paul, the easiest way to check that is to load it into a ServiceNow demo instance. I just did that at demo003.service-now.com and it seems to be working without issue there.

Okay i figured it out, with the Signature Pad script that is also on your site it doesn’t work in fact neither does the dynamic window. As soon as I pulled the signature pad out all of them started working instantly!

Very Strange. Currently on Calgary Patch 2 Hot Fix 11.

I will keep checking. Our scripts and setups are the same. Something just isn’t lining up.

I just installed it on demo004 and it’s working correctly there. You can test as ‘Itil User’ to confirm. The ‘report_on’ ACL works well, but for your situation you’ll want to start with a default deny ACL for all tables, then add permissions to allow reporting on specific tables from there.