This is our second wave of Excel O365 performance improvements after our first Sept ’17 one, to reinforce our commitment to fixing top impacting freezing, slow and not responding performance issues derived from Excel user feedback and usage learnings. This time around we have even more improvements than before starting with...

This is our second wave of Excel Office 365 performance improvements after our first Sept ’17 one, to reinforce our commitment to fixing top impacting freezing, slow and not responding performance issues derived from Excel user feedback and usage learnings. This time around we have even more improvements than before starting with...

Lookup functions VLOOKUP, HLOOKUP, and MATCH are one of the most used functions in Excel. If you use them with exact match to find items in a table or range in Excel, and see it noticeably take time in seconds or minutes or more, chances are you'll now see very noticeable improvement in the speed at which you see results.

We made them faster by more efficiently finding the item you are looking up. We create an index on-demand when you first search of a range of cells and then reuse it in subsequent lookups from the same range, until data changes in the lookup range. For details refer to our updated Excel Performance and limit improvements whitepaper.

Also, we have improved the speed of many use cases involving operations like copy/paste, undo, conditional formatting, cell editing, cell selection, scrolling, filtering, file open, and programmability, such as:

\n
• Copying the entire column in a sheet and selecting the clipboard is faster now because we optimized our large memory allocations with a more efficient data structure.
\n
• Undoing pasted cells with conditional formatting was slow because a paste operation was inefficient in generating an undo record for every cell with conditional formatting and with its own changed priority. It now combines them more efficiently into one undo record with changed priorities for all in it.
\n

\n
• Undoing inserting a new row with a copied range with merged cells is now faster because we optimized handing of merged cells during an undo operation.
\n

\n
• Deleting one or more rows with merged cells is now more performant because we skip redundant calls to render the visible grid in the midst of the deletion operation.
\n

\n
• Viewing filter drop down for a column with lots of cells with conditional formatting is now faster because we optimized the filter drop down algorithm to be more efficient computing highlight, unique, and duplicate values.
\n
• Scrolling in the visible sheet, after an operation wasn’t optimal, because we re-rendered (or at least evaluated) all rows top to bottom (including filtered rows) in the visible sheet. This can be expensive depending on the number of rows and our ability to calculate for animation related rendering. Our optimization introduced in our first wave of performance improvements
\n

\n
• Scrolling, editing of cells, cell selection, filtering operations in the grid are much faster when lots of rows are filtered / hidden because our rendering is more optimized to intelligently defer expensive rendering calls until we have calculated last row in the visible range.
\n
• Slow transitioning to the next cell after editing a cell adjacent to a large table or range of cells with data, because after editing a cell adjacent to a large table or range of cells with data, we would generate a preview of all cells in that column to Flash Fill, which is on by default. Depending on the size of the adjacent table or range of cells and whether the cells contain additional metadata like conditional formatting, this can be a time consuming and expensive operation. We now, limit scope of Flash Fill preview to the visible area improving Excel responsiveness. 
\n
• When opening any workbook we searched all existing ribbon content to ensure every component of the ribbon renders correctly. We have now made open faster by more intelligently searching in common cases like when the ribbon item being searched for doesn’t exist. Also, during open we now skip updating MRU links synchronously and instead update them asynchronously after open. Finally, we scope the rendering of the grid to the visible grid area when opening workbooks with lots of wrapped text in locales like Japanese.
\n
• Opening a local workbook when using a 3^rd party anti-virus software is faster because we are more intelligent in avoiding searching for the 3^rd party anti-virus vendor registered for scanning when a scan is determined to be redundant.
\n
• We open simple CSV text files much faster by employing a more efficient memory allocation.
\n
• Flashing scrollbars and slower running VBA code (than Excel 2010) even when ScreenUpdating property is set to false. We have addressed this by ensuring scrollbars will no longer update when ScreenUpdating property is set to false (just like in Excel 2010). This in turn diverts CPU cycles away from redundant rendering of the scrollbars and to running user VBA code, improving code execution speed.
\n
• Programmatically selecting a cell, a range of cells, or a sheet using VBA is faster because we avoid redundant calls for updating a document’s upload status when running VBA macro code performing operations like selecting a cell, a range of cells, or a sheet.
\n

\n
• Executing Frequency function for large data sets is faster because we optimized the underlying sorting algorithm for Frequency function for large data sets.
\n

Office 365 can help you be even more productive.¹ Give it a try today!

Now we know we are not done with this second wave and there is more, that said we would really like to hear from you to ensure our fixes align closely with the freezing, or slow, or not responding issues you experience. Hence please stay connected to Excel and its community, read Excel blog posts, send us a frown, and send us ideas and suggestions for the next version of Excel through UserVoice. You can also follow Excel on Facebook and Twitter.

Prash Shirolkar

Program Manager, Excel

¹ Available in monthly channel version 1809 or later

This is our second wave of Excel Office 365 performance improvements after our first Sept ’17 one, to reinforce our commitment to fixing top impacting freezing, slow and not responding performance issues derived from Excel user feedback and usage learnings. This time around we have even more improvements than before starting with...

Lookup functions VLOOKUP, HLOOKUP, and MATCH are one of the most used functions in Excel. If you use them with exact match to find items in a table or range in Excel, and see it noticeably take time in seconds or minutes or more, chances are you'll now see very noticeable improvement in the speed at which you see results.

We made them faster by more efficiently finding the item you are looking up. We create an index on-demand when you first search of a range of cells and then reuse it in subsequent lookups from the same range, until data changes in the lookup range. For details refer to our updated Excel Performance and limit improvements whitepaper.

Also, we have improved the speed of many use cases involving operations like copy/paste, undo, conditional formatting, cell editing, cell selection, scrolling, filtering, file open, and programmability, such as:

\n
• Copying the entire column in a sheet and selecting the clipboard is faster now because we optimized our large memory allocations with a more efficient data structure.
\n
• Undoing pasted cells with conditional formatting was slow because a paste operation was inefficient in generating an undo record for every cell with conditional formatting and with its own changed priority. It now combines them more efficiently into one undo record with changed priorities for all in it.
\n

\n
• Undoing inserting a new row with a copied range with merged cells is now faster because we optimized handing of merged cells during an undo operation.
\n

\n
• Deleting one or more rows with merged cells is now more performant because we skip redundant calls to render the visible grid in the midst of the deletion operation.
\n

\n
• Viewing filter drop down for a column with lots of cells with conditional formatting is now faster because we optimized the filter drop down algorithm to be more efficient computing highlight, unique, and duplicate values.
\n
• Scrolling in the visible sheet, after an operation wasn’t optimal, because we re-rendered (or at least evaluated) all rows top to bottom (including filtered rows) in the visible sheet. This can be expensive depending on the number of rows and our ability to calculate for animation related rendering. Our optimization introduced in our first wave of performance improvements
\n

\n
• Scrolling, editing of cells, cell selection, filtering operations in the grid are much faster when lots of rows are filtered / hidden because our rendering is more optimized to intelligently defer expensive rendering calls until we have calculated last row in the visible range.
\n
• Slow transitioning to the next cell after editing a cell adjacent to a large table or range of cells with data, because after editing a cell adjacent to a large table or range of cells with data, we would generate a preview of all cells in that column to Flash Fill, which is on by default. Depending on the size of the adjacent table or range of cells and whether the cells contain additional metadata like conditional formatting, this can be a time consuming and expensive operation. We now, limit scope of Flash Fill preview to the visible area improving Excel responsiveness. 
\n
• When opening any workbook we searched all existing ribbon content to ensure every component of the ribbon renders correctly. We have now made open faster by more intelligently searching in common cases like when the ribbon item being searched for doesn’t exist. Also, during open we now skip updating MRU links synchronously and instead update them asynchronously after open. Finally, we scope the rendering of the grid to the visible grid area when opening workbooks with lots of wrapped text in locales like Japanese.
\n
• Opening a local workbook when using a 3^rd party anti-virus software is faster because we are more intelligent in avoiding searching for the 3^rd party anti-virus vendor registered for scanning when a scan is determined to be redundant.
\n
• We open simple CSV text files much faster by employing a more efficient memory allocation.
\n
• Flashing scrollbars and slower running VBA code (than Excel 2010) even when ScreenUpdating property is set to false. We have addressed this by ensuring scrollbars will no longer update when ScreenUpdating property is set to false (just like in Excel 2010). This in turn diverts CPU cycles away from redundant rendering of the scrollbars and to running user VBA code, improving code execution speed.
\n
• Programmatically selecting a cell, a range of cells, or a sheet using VBA is faster because we avoid redundant calls for updating a document’s upload status when running VBA macro code performing operations like selecting a cell, a range of cells, or a sheet.
\n

\n
• Executing Frequency function for large data sets is faster because we optimized the underlying sorting algorithm for Frequency function for large data sets.
\n

Office 365 can help you be even more productive.¹ Give it a try today!

Now we know we are not done with this second wave and there is more, that said we would really like to hear from you to ensure our fixes align closely with the freezing, or slow, or not responding issues you experience. Hence please stay connected to Excel and its community, read Excel blog posts, send us a frown, and send us ideas and suggestions for the next version of Excel through UserVoice. You can also follow Excel on Facebook and Twitter.

Prash Shirolkar

Program Manager, Excel

¹ Available in monthly channel version 1809 or later

This is our second wave of Excel O365 performance improvements after our first Sept ’17 one, to reinforce our commitment to fixing top impacting freezing, slow and not responding performance issues derived from Excel user feedback and usage learnings. This time around we have even more improvements than before starting with...

sameer bhide , in general build number doesn't matter. It could include code for this or that functionality, but it is activated by channels and by waves within channel. That not at once for all users on the channel, even if they have proper build. Moreover, on insider channels functionality could be activated, in a while deactivated due to some issues and later on returned back with improved version. Exact activation schedule depends on many things, I don't think Microsoft will ever start sharing it. However, information like \"we activated this functionality for 100% of channel users\" could be useful. 

SergeiBaklan 

The problem is more with the messaging.

For e.g. I am on the current channel (preview) previously (insider slow)

As per https://learn.microsoft.com/en-us/officeupdates/current-channel-preview searchable validation drop downs rolled in to this channel on 26th Jan 2023 via Version 2301 (Build 16026.20094). 

I am currently on the most updated build of 14th Feb 2023 - Version 2302 (Build 16130.20156) and I still do not have this feature rolled out.

This is what is frustrating and there is no point is hiding behind \"Don’t have it yet? It’s probably us, not you\"

Cheers

Sam

Why not? That all is published here Office Insider Blog and that not only MVP:s who share information about new Beta functionality appeared with their own samples. You may check LinkedIn, whatever.

Beta actually is for testing purposes. Based on people feedback and stats collected Microsoft could change announced functionality on that stage. That happened with recent text functions, with smooth scrolling, some other functionality. Not sure if everyone is ready to use in production functionality which could be changed in few months.

And the question who is \"everyone\". If wait for semi-annual it could take more than an year.

I know they using the Insider, my point is they go out and advertise these new functions all over the place and gets everyone excited and then the waiting game starts.....  wait......  wait.........  wait.....

My point is, do not allow them to start sharing these unless you guys are sure it will be rolling out to everyone sooner than later (and usually it is MUCH later)

For example Leila Gharani showed us the new text functions already three months ago on her channel and still nothing in the roll outs.

Chris Botha , as a comment

1) How new functionality is rolling out is described here Overview of update channels for Microsoft 365 Apps - Deploy Office | Microsoft Docs and related links for insiders

2) MVP:s have no priority in receiving new functionality, they have it as any other Beta insiders. 

Thanks for this, but come on guys.  Where are the new text formulas.  Why are they not rolling out.  You are very eager  for your MVP's to make Youtube videos on all of these new features, just for us, the paying customer to wait months (if not more than a year) for them to roll out?  And don't tell me to join the programme for these pre-releases.  Excel with Windows 11 is not even working properly, can you imagine using these pre-release versions.  Somewhere Microsoft is going off the rails.  Seems you are more interested in getting more customers than actually providing the actual services.  I think I am your biggest fan since day one (Excel) but I am seriously considering moving to Google or Apple.  Make a rule regarding new functions rolling out.  Make a rule that MVP's are not allowed to share them unless they will be rolled out within the next month.  You keep hanging carrots in front of the donkey and not delivering.  And please fix the issues with Windows 11.  Excel just stops responding unless you move the scroll bar and then it wakes up again.  I am seriously loosing interest in my Office 365 subscription  (and we have more than 200 in our company).

在单元格格式对话框中：数字—特殊—大写，中能否在增加一个货币大写的功能呢？

Have you added Stockhistory?

Hello,

open the csv file, copy the Space between the numbers and replace them by nothing. Then it will be numbers and you can make calculations

In a calculation program made by Leica Geosystems, I receive a CSV with the followind data: The space between number 11 835,7777 it is not possible to change to my excel numbers (2nd table below- numbers without any space in between)  and therefore calculations are not made

Anyone cam help me ??