You’re offline. This is a read only version of the page.
The scope of this community post is to clarify the design of built-in “Open in Excel” (CTRL+E) action within Web Client and copy & paste rows from lists.
NOTE: this post is currently based on 16.3 build release.
Pages in the web client all show the button, but there are a number of scenarios where it may not be available, and the platform may not always know until runtime if this is the case or not for a given page.
Some of the scenarios where “Open in Excel” action is not available include:
Until version 14.x (included), you might have some of these pages like e.g. Item by Location showing the “Open in Excel” button but grayed out (disabled)
This is due to the limitation described earlier.
In version 15.x and later, you might notice that the action “Open in Excel” has been removed instead of showing it disabled by the platform to improve consistency within user experience (UX).
Whenever you hit this limitation, you still have the opportunity to copy and paste rows into excel. There is one extra that worth mentioning when copy / pasting that is officially reported here
Even if you have quite a lot of rows, selecting all rows (CTRL+A) and then doing a copy & paste will only add 50 records to the Excel spreadsheet. This is an intended performance savvy feature to prevent users (loading and) copying million of rows from a list. List pages are engineered to request only a limited number of records to be displayed as fast as possible, to request more lines from the server, users has to scroll down (this mechanism is also the source of high async_network_io on SQL Server side).
If user is really in need to copy all the rows, then he/she has to press CTRL + Page Down or scroll down until the last record being sure that all records has been fetched in the list. In that way, copy & paste will load into memory all rows and pasted into the Excel spreadsheet.
Last but not least, if users are copying quite frequently records from a specific list that does not have enabled the “Open in Excel” action, you might think of creating an ad hoc export to excel using a report or through excel buffer (if and where possible).
Share
Report
All responses (
Answers (
2,066
