Do you hate Merged Cells? Do you believe Merged Cells are evil? Do you curse every time your selection rectangle goes from one column to five columns just because you touched a merged cell? Do you constantly get workbooks from co-workers who continue to merge cells? Tired of not being able to Sort or Paste because someone merged a cell?

Excel encourages people to use Merge & Center by offering it front-and-center on the Home tab. Thus, few people discover the (superior) Center Across Selection option on the Alignment tab of the Format Cells dialog.

Currently, the Merge & Center drop-down offers: Merge & Center, Merge Across, Merge Cells, UnMerge.

My request: Adding a fifth item of "Center Across Selection" to the drop-down.

As a bonus, add a tool tip explaining the perils of merged cells and how Center Across Selection is superior in nearly every way.

Thanks for voting!

Incorrect values of dimension in pivot table sourced on OLAP cube (Microsoft SSAS 11.0.5569.0). The latest version without that bug is 16.0.6001.1068. Obviously we don’t know exact source of this bug, but most of the issues we discovered were on complex pivot tables with many attributes, partially displayed dimension’s hierarchy and without subtotals. Example of this bug occurring is in attached file ExcelBug. There are 2 exactly the same pivot tables (the table on the right hand side is basically copy of the table on the left hand side). After removing “Grand Total” on the table on the right hand side some fields have incorrect data displayed.
In this example field B4 contains correct value: „5 Name” (coloured green), field G4 (after removing grand total) contains wrong value: „6 Name” (coloured red).
Video https://youtu.be/RRwfAQVGBfc shows steps to change data source of pivot table and the bug itself. Files ExcelBugSSAS.abf and ExcelBugDBMSSQL.bak are backups of SSAS cube and database with all metadata and data to recreate this scenario in any environment (with SQL Server 2012).

There is a limitation to the width and height of a Content Pane at 1000 x 1000px. This limit is imposed when resizing via mouse in Excel Desktop and the JavaScript API. This (via mouse) is not true in Excel Online (or in PowerPoint) where the size can be set and saved to any size via mouse.

It would make the Content Pane consistent and open up a huge number of innovation opportunities to remove the current 1000 x 1000px limitation in the JavaScript API and Desktop Content Panes in Excel.

The ability to position and resize the Content Pane via the JavaScript API and Command Add-in would offer powerful opportunities for new applications and extending Excel functionality.

When you have one calculation-heavy workbook and distribute it to other people, it would be best if you could turn off calculation for only that workbook, without affecting the other workbooks these users are working on. It is confusing and outright dangerous in potential consequences that suddenly their workbooks do not calculate anymore. On the other hand, if the calculation is on, their whole excel freezes for a considerable amount of time every few keystrokes.

Suggestion: Allow for a transparent Manual vs. Automatic Calculation setting by workbook vs. a global setting.
There should be a popup when you open the workbook if the calculation has been turned off by the previous user of the document, giving you the choice to accept this (applicable only to the workbook) or activate the calculation again.

Merging cells has the drawback, that it cuts the functionality of the excel file.
So why not implementing a functionality, that merges cells ONLY OPTICALLY, so that the cells still keep their value and thus the full functionality, but that excel recognizes, when cells in rows that are directly located under the each other, contain the same values and thus just merges the cells optically, but does not merge the values, so that the user sees the merged cells on his monitor, and is able to print the table with merged cells, but still can e.g. sort the rows in the table because each cell still functionally contains its value.

It's about time to improve support for SSAS Tabular:
1. Auto-generate DAX
2. Avoid splitting a table into a "measure group" and "dimension". See how PBI Desktop handles metadata.
3. Carry over data types so that users can create reports, such as show me invoices where Due Date is greater than ... Currently, all dimension table fields map to Text.
4. Many customers have expressed interest to connect Excel tables directly to Tabular, bypassing Pivot Table, so they can use the column dropdowns and other Excel goodness.
5. Support descriptions as tooltips when the user hovers on a field in the Field List.

Allow users to create formulas and that perform specified operations with data/values from only cells with a chosen background color, from a range of cells.

For example, in a range of 10 cells (A1:A10), only 3 cells have been colored yellow (either by the user or by a specified condition). A user can create a formula, such as =SUM or =COUNT or =AVERAGE, that will only use the cells colored yellow to determine the result. All other cells in the range, regardless of background color, will be excluded from the formula's result.

Alternatively, the same functionality can be achieved based on font color, such as values colored red.

Ideally, both methods (cell background or font color) should be implemented since the use of color is a very important and natural way users identify special or standout data. Even on paper we use highlighters of various colors, or red-ink pens to identify data or values of special importance. The most powerful and useful spreadsheet software available should also have this capability, without requiring users to develop complex VBA scripts and code.