Published Report not Showing Any Data

[adamrauh]

Hey guys, I'm sure this is related to either an ECL or Business rule for querying the table, but so far my changes haven't worked, so looking for some help.

I'm trying to publish some reports (first, below, is on the incident table, but there will also be more on the request and task table) for non-itil users to be able to view.   When I look at them (obviously, as an ITIL user w/ admin/report admin) they look fine, but when I imitate one of the users, I can't see any of the list data.

(as me,data is covered, but the line items are there):

(as my test user w/ a non-itil role, no data showing):

Any ideas?   They should only be able to read the data, not access it.   Also, I would like to use best practices w/ concerns to security, so whatever least rights are available and not use up an extra license.

[Uncle Rob]

By default, non-roled users are typically only allowed to read Incidents (and other OOB task types) in which they are the "for" (in Incident's case, "caller") or where they exist on the watch list.   Usually though, the user will get an error showing how many rows were redacted due to ACLs.

First thing I'd do is build a report showing ONLY where your non-itil test user is the caller and see if they get any results.   That should tell us whether the issue is ACL based or something else.

RDF

[ggivner]

The problem that I'm finding with Published reports is that even if the user has roles in SN, if they are not logged into the application, then the report comes back as showing no tickets with no other message.   They go back and log into Service Now, click on the published reports again and are able to see them.   This happened to me this morning - why is this happening like this?

[ggivner]

After additional research in the wiki, I found this:

Publish a report to create a URL that you can easily share with other users on your ServiceNow instance. Users must be logged in and have an appropriate user role to view the report

Evidently, you have to logged in to SN in addition to having roles.

[Sumit Maniktala]

There is no need to login and even if you don't have an account than also public reports are viewable

There are couple of things here

1. Make sure the report you have created has Public role aligned to it. You can check this by going to Report->Administration module

2. Make sure you have read ACL defined on the table on which you have based your report & that ACL has Public role aligned

3. Make sure there is no Query business rule running on the table on which your report is based (like for incident we have one called 'incident query'). These BRs generally filters the records based on certain criteria

Keep in mind that opening these resources to Public role means they are available on internet without restrictions (though read only)

Hope this helps