Excel for Windows (Desktop Application)
Welcome to the Excel for Windows (Desktop Application) feedback forum! This is the place for users to send us suggestions and ideas on how to improve. If you think you have found a bug, please send us feedback in-app instead! To do so, please click “File”, then “Feedback”, then “Send a Frown” in Excel. This way, we will get detailed information that will help us better diagnose the problem.
To help us build the best version of Excel ever, we have partnered with UserVoice, a third-party service, to create this site to hear your suggestions and ideas for the next version of Excel. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.
-
Add the ability to hide columns in the Power Query Editor
Users should be able to Right-Click on a column in the Power Query editor and have the option to hide the column from view when it is loaded. Currently the only option is to completely remove the column altogether....
10 votes -
Range.Text should be able to return an array of results like Range.Value
Range.Text should be able to return an array of results instead of only being able to return the text for a single cell. Its behavior should be consistent with Range.Value and Range.Value2.
Additionally, Range.Text should never return a result like '#####' when the column width of the cell is too small. It should always return the text that would be visible if the column was wide enough (and calling Range.Columns.AutoFit before calling Range.Text should not be necessary).
36 votes -
Fix errors and incompleteness in macro recording
The macro recorder is a highly valued feature of Excel and is used by novices to generate code to automate repetitive operations and by more expert users as a quick way to confirm the appropriate properties and methods to use to achieve a desired effect.
There are some operations that the macro recorder does not record at all and others which it records incorrectly. This suggestion is that all such errors and omissions should be fixed when they are identified.
The latest to come to my attention was assigning a formula to a shape, to link its text to a…
23 votes -
add the vba range.NoProofing property to Excel, like Word and Outlook have
the Range.NoProofing property would let you mark ranges, cells, table rows or columns as exempt from Spell checking.
Outlook and word have this property and it helps prevent pollution of the custom dictionaries.
4 votes -
R in Excel (RRO + MKL as scripting language in Excel)
Microsoft recently acquired Revolution Analytics:
http://revolutionanalytics.com/
Revolution R Open with MKL is an open source derivative of R (RRO + MKL). Adding-in RRO to Excel is a natural fit and will extend the scripting utility of .xlsx in Enterprise environment. The package developments alone are worth considering this integration.
149 votes -
recover ribbon pointer
When programming the ribbon in VBA, if the code is ended, the ribbon pointer is lost and there is no means of recovering it without reopening the workbook. It should be possible to recover the ribbon object. (There is an unofficial workround involving copying memory, but this is hardly desirable).
3 votes -
Power Query Self Appending Queries
Power Query Self Appending Query
I've built a few self appending Power Queries by modifying the M in advanced editor - It would be nice to have the functionality built into the GUI.
The Query would read the loaded query data from the related ListObject (or data model) into memory while asynchronously querying another data source. The data from the other data source would be append to the previously loaded data set then either load the table or load back to the data model after removing duplicates(optional).
7 votes -
There should be a WorkbookAfterClose event
there is a WorkbookBeforeClose event but there is no corresponding WorkbookAfterClose event.
Note that the WorkbookBeforeClose is cancelable so there is no guarantee that the workbook will actually be closed after that event is triggered.
Currently in order to get the WorkbookAfterClose event, a workaround needs to be implemented: https://exceptionalcode.wordpress.com/2010/02/11/how-to-get-an-excel-vsto-workbook-closed-event/
21 votes -
There should be a Range Difference function in addition to Union and Intersect
There are functions to get the intersect or union of two ranges, but there exists no built in function to get the difference between two ranges.
When I say difference, I mean A - B = A ∩ B' where B' is the complement of B
4 votes -
Spreadsheet Compare - use original number format when exporting results
The Spreadsheet Compare tool included in Excel 2013 and the Inquire add-in has the ability to export the results of a comparison to a new spreadsheet in a handy tabular format.
However the "Old Value" and "New Value" columns are formatted as text. If the number format in the spreadsheets being compared was "number, one decimal place", the Spreadsheet Compare output looks like this:
22.0 (21.990702621768023)This makes it difficult to compare Old Value and New Value using formulae because one first has to strip out the value between parentheses and convert to number.
My suggestion is to output the…
6 votes -
barcode
Add a barcode insert for Excel. Rather than relying on 3rd party applications.
9 votes -
Adding WorkSheet.BeforeChange event in Object Model
Worksheet Object does not fire a Worksheet.BeforeChange or Worksheet.Changing event. For our use case, which is for auditing and potentially preventing changes done to Excel Sheets by specific users, we get the event after things have changed.
We have a specific set of cells that should changeable by only a few users so we use .net interop to get user credentials from Active Directory.
14 votes -
C# as a scripting language
Let us code macros directly in C#!
47 votes -
Fix object model implementation of Top10 Auto Filters
The current implementation of the Top10 auto-filters in Excel is horrible.
There are four 'Top 10' filters: xlTop10Items, xlTop10Percent, xlBottom10Items, xlBottom10Percent
Problem 1) The names are deceiving. They are not always 10 items or 10 percent. Better names would be Top X Items or Top N Items.
Problem 2) The Excel object model does not allow the original criteria to be retrieved. If you create a Top 10 Items filter with the value 15, then the Filter.Criteria1 property will be changed to a >= criteria depending on the data in the column and the original value of 15 has no…
7 votes -
5 votes
-
Make it posible to attach a template to the Empty Workbook-option on the Start Screen and File, New
In previous versions of Excel you could create a Book.xlt and make that the default template for new workbooks by saving it in the XLSTART folder. That does not work with the Start Screen/Back Stage in Excel 2013 and 2016 which makes it imposibole to provide customers with a custom template for new workbooks with customized colors, fonts etc. Please make it posible to attach the Empty Workbook option to a customized template. (It still works in Word 2013)
26 votes -
Safe Macro Detection
Certain types of macros could be guaranteed to be safe to the user of a workbook. Such an example would be a UDF that does pure numerical manipulation.
I propose that there is some mechanism to detect whether VBA could have unwanted side effects and block those, but workbooks containing only VBA that does pure numerical manipulations or makes use of only other worksheet functions should be enabled by default.6 votes -
Remove the 255 character limit in Excel object model functions
The parameters of some VBA functions have a 255 character limit which makes some functionality impossible.
Examples:
* Worksheet.Evaluate()
* Application.ConvertFormula()32 votes -
Expose more events in VBA
Please can we have the OnKeyPress, OnKeyUp and OnKeyDown events exposed in Excel please?
It is a real and unnecessary pain to have to use the API to do this simple thing.
57 votes -
Worksheet protection - UserInterfaceOnly setting should maintain between workbook openings
When developing VBA and/or VSTO solutions for Excel, you might come across the problem that a protected worksheet where the UserInterfaceOnly parameter was set to "True" cannot save its state to the next Excel session. This means that the UserInterfaceOnly setting cannot be maintained between workbook openings. Therefore, to re-establish the setting you have to unprotect and re-protect the specific worksheet (for example during the Workbook_Open event). Unfortunately, since Excel 2013 this might be a performance issue when handling a lot of worksheets (see https://msdn.microsoft.com/en-us/library/office/ff837594.aspx?f=255&MSPPError=-2147217396#xl15WhatsNewProtectingsheets - "Protecting Sheets takes longer"). On a modern desktop computer you would probably not even…
18 votes
- Don't see your idea?