Export to Excel file does not download exact number of rows displayed in list view. Any suggestion ?

Amarendra
Mega Contributor

‎03-15-2016 04:13 AM

Export to Excel file does not download exact number of rows displayed in list view. e.g- i can see all active notification which says- "1 to 300 of 323" on a page when i export it to Excel it downloads only 303 rows. I am using Eureka release.

0 Helpfuls
  • 3,163 Views
11 REPLIES 11

sergiu_panaite
ServiceNow Employee
ServiceNow Employee

‎03-16-2016 02:42 AM

Hi Amarendra,



Do you have access to view all 323 rows? If an ACL is restricting you from seeing all 323 then you would not be able to download the restricted ones, but still in the list view it will show you the total number.



See below example, in list view I see a count of 1378 rows but ACLs are preventing me to actually view any rows data:



Screen Shot 2016-03-16 at 10.39.44 AM.JPG



The other thing that can restrict the number of rows export is a limit imposed on Excel export, but I would find it strange to be set to 303



Exporting Data - ServiceNow Wiki



Regards,


Sergiu


Preview file
78 KB

Amarendra
Mega Contributor
In response to sergiu_panaite

‎03-24-2016 07:54 AM

Thanks Sergiu ! I checked export limit which is set to 18000. Seems like an ACL issue, but which "operation" corresponds to exporting records to excel ?


0 Helpfuls

sergiu_panaite
ServiceNow Employee
ServiceNow Employee
In response to Amarendra

‎03-24-2016 08:02 AM

Hi Amarendra,



As admin you can do System Security -> Debugging -> Debug All Security and try to load the list view. Once list view is loaded, it will display below which ACLs you're failing.



Don't forget to disable debugging once you did the test.



Regards,


Sergiu


0 Helpfuls

ghsrikanth
Tera Guru

‎03-24-2016 07:12 AM

The ACLs always 'deceive', when ACLs restrict the records, it will list all the records in Count near to the pagination (50 of 2000 records) but it wont show any record.


We have to click next button to see all the records.


But the use of Query BR will help us to view everything neat, there wont be any message "Security Constraints: 50"


I always prefer query BR - one more security that comes with Query BR is


When the table is Glide Queried through script   - the ACLs wont be honored   the records can be accessed through Glide script


In case of Query BR, it wont be possible.



Controlling record access using 'Before Query' business rules - ServiceNow Guru


Even platform code uses query business rule to access the platform tables through Domain Separation.



Hopefully it helps


0 Helpfuls