Published reports do not show all expected dataIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When you publish a report, external users may see different data than internal users. This article describes the most common causes of data discrepancies in published reports and how to resolve them. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The following sections describe the most common causes of data discrepancies in published reports and how to correct each one. Fewer rows than expected in list reports In a list report, unauthenticated users may see fewer rows than logged-in users, or no rows at all. When rows are removed, a message typically appears indicating that some groups were removed from the list by security constraints. Cause: In any list report, each row is evaluated against the Read ACL defined on the source table. Unauthenticated users are treated as the guest user, so the ACL is evaluated in the context of that guest user. Resolution: Create a new ACL or update an existing one to give the guest account access to the records that should appear in the list report. The guest account corresponds to the public role on the instance. Note: Take care to confirm that no data that should not be shared publicly is displayed in a list report. Creating or modifying an ACL record requires an admin account elevated to the security_admin role. Graphical reports showing incomplete data A graphical report (any non-list report type) may show fewer data points for unauthenticated users than for logged-in users. Cause: Before query business rules run on source table data before the report is rendered. If these rules restrict data based on user permissions or roles, unauthenticated users — treated as the guest user with no groups or roles — see only the records that pass those restrictions. For example, the base system Before Query Business Rule on the Incident table returns only records where the current user is on the Watch List, is the caller, or is in the Opened by field — and only if the user does not have the itil role. Because the guest user has no roles, only records where guest appears in those fields are included in the published report. Resolution: Modify the applicable before query business rules on the source table to allow access for guest users or all users. Options include: Adjusting the condition so the business rule does not apply to users with the public role.Deactivating the business rule.Modifying the script to not restrict access to these records. Note: These same before query business rules also apply to rows in list reports. However, because list report rows are usually more restricted by ACLs, this issue is less common in list reports. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Important notes on published reports After you unpublish a report, the previous public URL is no longer valid for any user, logged in or not. Accessing that URL displays a page not found message.For testing purposes, log out of the instance before accessing the public URL to see what unauthenticated users see. If you remain logged in, you may see the report as a logged-in user rather than as the guest user. How to check if a report is published To check whether a report is published, go to Reports > View / Run and select the appropriate tab (My Reports, Group, Global, or All). Reports that are currently published display a blue circle with a check mark in the Published column. Alternatively, open the report for viewing or editing. A published report displays the Copy Report Link icon in the top menu bar. You can also open the report and select the Sharing icon. A published report shows an Unpublish option; an unpublished report shows a Publish option. You must have the appropriate permissions for these options to appear. How to get the URL for a published report Open the published report for viewing or editing and select the Copy Report Link icon in the report toolbar. The full report URL is copied to your clipboard and a confirmation message appears. The URL follows this format: https://<instance_name>.service-now.com/sys_report_display.do?sysparm_report_id=<sys_id> Where <instance_name> is the name of the source instance and <sys_id> is the unique system identifier of the report record. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } KB0727099 - How to Publish or Unpublish a Report (Report Designer Interface)KB0728025 - How to Publish or Unpublish a Report (Report Builder Interface)