Ed Hansberry
My feedback
-
758 votes138 comments · Excel for Windows (Desktop Application) » Editing · Flag idea as inappropriate… · Admin →
Thanks again for all the passion on this issue – we hear you and we’ll get someone on the team to dig in to the issue. I’ve seen a few related sub-issues while scanning over the comment section for this one, so we may reach out to a few of you for clarifications. Thanks again for all the votes, and keep them coming for the issues you care about!
John, Excel
Ed Hansberry
commented
Roy, MDI and SDI don’t affect the number of instanced of Excel. Still one instance. SDI allows us to move files between monitors though.
Ed Hansberry
supported this idea
·
-
309 votes40 comments · Excel for Windows (Desktop Application) » Formatting · Flag idea as inappropriate… · Admin →Ed Hansberry
commented
Center Across Selection should be the default action as it has the least amount of side effects (destroying ability to sort, causing problems for Tables, adding data to Power Pivot or Power Query, etc.)
Ed Hansberry
supported this idea
·
-
879 votes305 comments · Excel for Windows (Desktop Application) » Formulas and Functions · Flag idea as inappropriate… · Admin →
Progress! As of this morning, we’ve begun enabling the first iteration of Excel’s new data types for a percentage of Office Insiders, including the ability to pull and refresh live stock quotes (and other financial data) straight in to Excel! We’ll be increasing the percentage of Insiders with access to the feature over the coming days and weeks, so if you don’t see it right away please hang in there!*
We acknowledge that right now this is only half of the suggestion (pull current stock prices), but historical data is in our sights and we’re planning to add this and many other improvements to stock and financial data. Your feedback thus far has been immensely valuable in helping us plan and design this work, and we look forward to your continued suggestions for how we can improve to better meet your needs
Again, we genuinely appreciate your involvement as we…
Ed Hansberry
commented
@lars - I'll have to check my mac at home to see if it is there. I know it already has the Dynamic Array functions introduced about a month ago to Windows Office Insiders. Now that the calculation engine for Excel on all platforms is the same, features roll out much faster to each platform - usually within months.
I do know Excel Online doesn't have stock quotes yet.
Ed Hansberry
commented
I am sure it will be in the stand alone version of Office 2021/2022. It wasn't ready in time for Office 2019.
Ed Hansberry
commented
@barbara - you have to be an Office 365 user to get on the Insider program. It is free to sign up if you are on O365. See https://products.office.com/en-us/office-insider?tab=Windows-Desktop for info.
Ed Hansberry
commented
Good grief people. Microsoft didn’t disable anything. Yahoo pulled the plug. I hope MS will get another partner on this, or do it themselves is MSN Money. To think this is illegal...LOL
Ed Hansberry
commented
This is the risk of using a service you don’t control. Too bad Yahoo dropped this feature. Would be nice if MS added this ability via MSN. Of course Windows users can use Power Query/Get & Transform in Excel 2010 and higher, but that doesn’t help Mac users.
Ed Hansberry
supported this idea
·
-
28 votes6 comments · Excel for Windows (Desktop Application) » Data Import · Flag idea as inappropriate… · Admin →Ed Hansberry
commented
Excel has a button to clear all links in Data|Edit Links, but it only seems to work well on links in cells in the spreadsheet, not links in the Name manager, or hidden or more obscure links. That button should wipe out ALL links.
Ed Hansberry
supported this idea
·
-
142 votes16 comments · Excel for Windows (Desktop Application) » Other · Flag idea as inappropriate… · Admin →Ed Hansberry
commented
Honestly, I'd be ok if we just got the "Center across columns" button. ;-)
Ed Hansberry
supported this idea
·
-
9 votes0 comments · Excel for Windows (Desktop Application) » PivotTables and Power Pivot · Flag idea as inappropriate… · Admin →Ed Hansberry
supported this idea
·
-
6 votes1 comment · Excel for Windows (Desktop Application) » Formulas and Functions · Flag idea as inappropriate… · Admin →Ed Hansberry
shared this idea
·
-
1 voteEd Hansberry
shared this idea
·
-
8 votesEd Hansberry
supported this idea
·
-
29 votes1 comment · Excel for Windows (Desktop Application) » Charting, Mapping and Visualizations · Flag idea as inappropriate… · Admin →Ed Hansberry
supported this idea
·
-
420 votes
Thanks for your feedback! We’re reviewing your suggestion. I would like to clarify: If sharing through SP the URL parameters are hashed. When a user edit an Excel file and copy the URL for sharing over email the user can choose to change the action to edit.
Remember, the more votes a suggestion gets, the more likely it is that we’ll do it.Tamar [MSFT]
Ed Hansberry
supported this idea
·
-
1,490 votes
Thanks for all the votes and comments on this suggestion. We know this is important and it’s a big undertaking. Please continue to show your support for this.
Steve K [MS Excel]
Ed Hansberry
commented
@nathan - the price is for office 365 in general. You install whatever version you want for your computer OS.
Since the price for the Windows version didn't increase with the addition of Power Query or Power Pivot, I'd surmise they consider that free enhancement.
All that said, I want this on my Mac as well, but there is no pricing disparity.
Ed Hansberry
commented
If you read this thread on Answers, it looks like MS is making some internal progress on this feature... at least the Mac recognizes there is a data model. https://answers.microsoft.com/en-us/msoffice/forum/msoffice_officeinsider-mso_mac-msoinsider_excel/workbook-using-a-new-feature-in-excel-for-windows/8f18af1c-d9df-40e1-8646-49a0d22ffb85
Ed Hansberry
commented
Google has Power Pivot?
Ed Hansberry
supported this idea
·
-
1,931 votes278 comments · Excel for Windows (Desktop Application) » Data Import · Flag idea as inappropriate… · Admin →
Hi all,
I wanted to share with you that the new query caching mechanism in Excel has been deployed to Office Insiders starting from Excel version 1801 (build 9001.*). At this stage, we would like to allow some “baking” time as we monitor the feature health metrics.
In this scope, we need your help to ensure a quality release! I encourage you to try the following scenarios and share your feedback:
1. Run Refresh All on a complex workbook with multiple query dependencies. Does it work faster?2. Run Refresh All on a complex workbook with multiple query dependencies. Do you see any issues with your data?
3. Refresh a single query several times. Do you see any issues with your data?
- The Excel Team
Ed Hansberry
commented
@Adam - anyone with 1801. The only people that won't ultimately get it are those that purchased a perpetual Office 2016 license.
It will be in Office 2019 this fall too.
Ed Hansberry
commented
@nickolas, it depends heavily on your data source. If it is a bunch of CSV files, then those are pulled in. If they are on Sharepoint/Onedrive, that can take even longer. If it is SQL Server, then it depends on how efficient your queries are and take advantage of query folding. This is one of those "it depends" based on the source (of which Power Query supports several dozen) and how efficiently you are using them.
Ed Hansberry
commented
@Nicolas - not all models will see an improvement. If your model calls the same data repeatedly through queries that are referenced by other queries, this enhancement will cache the data from the first query and let the 2nd, 3rd, etc. use it without pulling the data again.
If your models don't do much/any of that, then this wouldn't show much of an improvement if any.
Ed Hansberry
commented
@adam - it is in build 1801 of Excel or later for Office 365 users. Insiders, Monthly Targeted, and Monthly users should have already. Deferred channel may already have or be getting soon depending on how the IT department is rolling it out.
If you have Office 2016 perpetual license, you'll either have to purchase Office 365, or purchase Office 2019 perpetual when it comes it. AFAIK, it won't be pushed out to 2016 perpetual licenses.
Ed Hansberry
commented
@inetguru - never. You have to have office 365 subscription for new features. Or buy 9office 2019 when it comes out. But that will not get new features after it is released either. Just security and bug fixes.
Ed Hansberry
commented
@admin how can we tell if this runs faster? We are on the monthly targeted release and therefor have had this since Jan 2018. No way to know if it runs a faster. I cannot recall how something ran with build 1712.
Ed Hansberry
commented
@anon- if you don't have Office 365, meaning you have a perpetual license for 2016, you'll have to buy Office 2019 or subscribe to Office 365.
If you have Office 2010 or 2013, then I don't know if/when they will add this functionality to that Power Query addin. I kinda doubt they will, but who knows. But I doubt they will issue an update to Office 2016 perpetual license users. They never issue new features for perpetual licenses, just security updates.
Ed Hansberry
commented
@lauren - you absolutely need the data model to build pivot tables using Power Pivot, which gives you the ability to use multiple tables, relationships, measures, etc.
if you aren't using the data model, then you are using pivot tables the old way which requires a single flattened table in a spreadsheet. Horribly inefficient the larger the table is.
Ed Hansberry
commented
Thanks Rory. I actually use a dropdown in a cell in Excel to feed the source server info to the original SOURCE statement.
I don't want it automatic as sometimes I may want Power Query to ping my SQLEXPRESS copy even if at work if I am working with tables that rapidly change during the day, making troubleshooting and figuring stuff out a pain.
But interesting use of the try statement. :-)
Ed Hansberry
commented
@martinG - that is a good practice. I didn't know it sped things up. I do it because I keep replicas of some tables on my PC in SQL Express from our SQL Server so I can develop reports when not in the office. I simply change one data source in the query and dozens of tables automatically update to my local install, then I change it back when I get in the office or push to production.
Ed Hansberry
commented
"Hey please speed up the engine of Excel query b4 moving on to other less relevant features. "
AMEN! I am sure it isn't the same team, but when I am tapping my fingers on my desk waiting for PowerQuery to refresh itself after I simply rename a step and I see a blog post that now we have Lava Ink in Office when drawing, I want to throw my computer off of my desk.
Ed Hansberry
supported this idea
·
-
1,458 votes436 comments · Excel for Windows (Desktop Application) » Editing · Flag idea as inappropriate… · Admin →
Thanks very much for your votes. And to those who took the time to fill in the survey, thank you! This is a brief update to let y’all know that we’ve started work on this feature request.
- Urmi [Msft]
Ed Hansberry
commented
Thanks Urmi. I'll be very curious to see how this will be implemented without impacting previous models.
Ed Hansberry
commented
@exacerbated. Yup, definitely happens. It is now second nature for me to press the windows menu key (usually to the right of the space bar), and the SV.
That is Paste Special, Values.
What is happening is the cell is formatted text, you are copying from somewhere else, even another app, and it brings a number format with it, then excel trashes it.
If you paste as values, only the raw ASCII gets pasted in there, no formats, so the Text format in Excel persists.
Ed Hansberry
commented
@Exacerbated - make sure the table column with the long digits is formatted in Excel as TEXT format. Editing/entering data will retain the text format and not convert to a number or lose precision.
Ed Hansberry
commented
Power Query isn't a third party addon. And for importing text files, the learning curve is almost nil. It is far easier to use than the depreciated Text Import wizard, and far more accurate than just clicking on a CSV file and hoping it reads your mind.
Ed Hansberry
commented
@corin - what you refer to is not the same thing. A part number with an "E" in it is not the same issue, but you are correct, Excel will try to convert to a number thinking it is scientific notation, unless you use Power Query (which you should) where you can tell it to leave that field as text. No one should be importing CSV files via plain old Excel if they want any level of control. Import via Power Query and get 100% control over every field.
Ed Hansberry
commented
If you type in 123456789 into a narrow cell, it will change it to 1.2E+08 visually, but if you change the cell format to comma, currency, or whatever, it has retained 123456789 as the full precision.
Ed Hansberry
commented
Ok. that is massive. M.******I.V.E. They could be working on that, but that would literally involve changing every single function that deals numbers (so all but the text functions), tables, pivot tables, Power Query, Power Pivot, Power Map, the Power BI enterprise app, Data Gateway, which all rely on the same 15 digit precision.
Ed Hansberry
commented
It does that Zak. The issue only becomes an actual data problem when there are more than 15 digits. Excel cannot handle that so if you put in an 18 digit number, regardless of how it displays, it will change the last 3 digits to zero - unless you enter it as text.
Ed Hansberry
commented
I see you've never talked to corporate lawyers before.
And much like you have shot down my ideas on using Power Query which resolves about 95%-99% of the issues in this thread.
Have a nice evening.
Ed Hansberry
commented
You cannot put anyting on sheets taht isn't saved. It is automatically saved. You would have to close it, delete it, then empty the trash, and even then, not sure if there isn't a 2nd level trash can it is stored in for a while. Office 365 has that.
And again, in a big corporation, permission for that involves lawyers, not your boss.
Ed Hansberry
commented
Some of you don't understand how large corporations work. An employee can get fired for putting company data on ANY unapproved cloud solution.
Ed Hansberry
commented
@Scott, Power Query does exist. The G&T name is for the Excel UI, Once in the query UI it is still referred to as Power Query, and is also used in Power BI.
As to complexity, for handling CSV files, you don't need to know any M code. It is all push button in the UI.
As for DAX, if you are using DAX in side of Excel via Power Pivot, you must learn Power Query. PQ is where you bring in your data, clean it, and create a structure for your data so it fits a clean Star schema, which is where DAX shines.
I found out the hard way bringing in data directly via DAX was going to be a train wreck for all but the smallest data sets.
Ed Hansberry
commented
@Corin, I think your mention of PowerShell is the first in this thread. I know PS is very powerful, but I have no idea how you'd use it with CSV files.
Ed Hansberry
commented
Jody, solid workarounds (namely, Power Query) have been shown how to 100% avoid this issue EVERY SINGLE TIME, but some on this board would rather just rant.
You are spot on RE: Google Sheets. Compared to Excel, that platform is a joke. It is like comparing a word processor to Notepad.exe.
Ed Hansberry
commented
@corin - yes. You'll need to manually edit the code, but absolutely. http://www.thebiccountant.com/2017/01/09/dynamic-bulk-type-transformation-in-power-query-power-bi-and-m/
Ed Hansberry
commented
Corin and Todd, I only did the simplest of steps for a single file. I have power queries that look at a folder and always import the most recent two files which can be done based on file date OR contents of the file, such as an ASCII print header or text field, and then compares them. The file names are irrelevant in those cases.
Export. Save. Refresh.
That’s it.
Ed Hansberry
commented
@corin - I never said people were relying on scientific notation. I said they were relying on the way it works today and have coded, made workflows, or formulas that handle it as is, then modify it as their needs dictate. If you change how the data comes in, that all breaks.
My solution is not hacky - far from it. You should learn how to use Power Query. Try my steps and get a feel for it. This is what it is FANTASTIC at doing. You do the many steps ONE TIME. Your steps are recorded. Then you just refresh all and all those steps are applied again with a new CSV file. It is the total opposite of a hacky workaround.
I never said MS ignoring it for decades was ok. I said the system has existed as it is for decades, and as such, people have modified their models accordingly. Furthermore, MS is NOT ignoring it. They addressed it above, and they addressed it in the Reddit AMA earlier this week. It is on the table for discussion, but I know a big sticking point is how not to break models that have been in existence for years, or decades, by changing behavior of what Excel does while still making it easier to work for people that don't know about Power Query, or that consider such an approach "hacky." LOL!
Personally, with the advent of Power Query in Excel 2013, I would NEVER import a CSV file like you are doing. PQ gives me the ability to fix each field as I need, adjust the contents as I need, then dump to a table *EXACTLY* the way I want it, and then it does it day in and day out, months on end and I am never surprised at the results because I. DO. NOT. LET. EXCEL. MAKE. ANY. ASSUMPTIONS.
PQ lets me control 100% of it. It works with leading zeros, text like 6E034, 50 digit numbers, etc.
I personally don't care what MS does in this regard because I use the Power Query/Get & Transform model to control the data.
What is hacky is double-clicking on a CSV file and then modifying it to suit your needs every time.
Continue on though. I was just trying to give you a real world solution that works today hoping to save frustration until MS does whatever they will do whenever they may do it, which might be nothing and never. Or it could be a magical solution that pleases everyone and be released to the fast ring tomorrow. My solution is there today though, and I'd bet money if many people implemented it, they wouldn't even notice if MS ever did anything about the CSV import via the file menu or the old now depreciated Text Import Wizard.
Ed Hansberry
commented
Daniel, not sure why the query method fails for you. This works 100% of the time for me:
1) Data, Get Data (This is Excel 2016 - Excel 2013 is the Power Query addin)
2) CSV file
3) Edit button
4) Change Data Type to Text - tell it to "Replace" if it converted to a number first, which it did with my credit card number test.
5) Close and Load to a sheet (or data model if you need this in a Pivot table)Even preserved leading zeros.
Save the Excel file.
Get new CSV and drop it where the old one was with the same name.
Open Excel File, Data Tab, then REFRESH ALL.
Works every time.
Ed Hansberry
commented
What was fixed in a later release?
Also, I assume nothing. MS assumes they know how their product is being used by both regular users and fringe users, and they won't change something that breaks it for either.
Ed Hansberry
commented
It isn't a simple thing to fix. Right or wrong, this is how it has worked for literally decades. Millions of spreadsheets are set up to work this way, and then adjust accordingly if the user wants the end result to be different.
If MS "just changed it" millions of models would break overnight. So they have to move carefully to provide a better answer. Google doesn't have this problem. Their sheet is new and they did whatever they wanted to do, and honestly, if it changed something, some would complain, most wouldn't notice, and fewer would care. Excel is very different. Databases are built on it. Visual Basic code is built on it. .COM addins are.
I know MS is working on this very issue. It was in their recent Reddit AMA on Wednesday of this week. But it is far from a "fairly simple issue to resolve."
And the funny thing is, 99.9% of the issues in this thread are avoidable by using the Get & Transform feature in Excel 2013 and 2016 (also known as Power Query) or preformatting cells as text. So it isn't like you cannot use Excel to get the job done. You just have to do a few extra steps that actually GUARANTEE you the results you are looking for vs having the app make the decision for you.
Ed Hansberry
commented
Zak, it isn't about using an inaccurate number. It is about using a number where you can trust the number of significant digits. Most numbers in science are rounded to some number of significant digits, unless you know exactly. For example the number of people on this thread fighting windmills is 1. Exactly 1. That is an exact and scientific number.
Ed Hansberry
commented
I suspect this is the fix, which will be part of Office 2019 released in 2018. Just speculation though. Not a lot given in this announcement.
https://techcrunch.com/2017/09/26/microsoft-excel-is-about-to-get-a-lot-smarter/
Ed Hansberry
commented
Seems to me a lot of this could be fixed if there were some addtional "autocorrect" options for Excel that we could disable.
*Stop changing text to dates. If I type "Oct 2015" then I want "Oct 2015" in the cell, not 10/1/2015 formatted as MMM-YY
*Stop changing math to dates. =9/12 is not my way of telling Excel to convert it to Sept 12 in DD-MMM format.
*stop changing math to fractions. I cannot repro an example right now but too many times I've entered something like =8/6 because that is what I need in the cell but Excel will change it into a fraction, causing me to undo/redo until it stops.
*The large numbers issue here (though that won't address people importing digits larger that 15 places as that is the max excel handles, all the rest becoming zero)Ed Hansberry
commented
@zak - load two files (your favorite - CSV files) of something modest. Say 200,000 rows, 10 columns for one file, and 5,000 rows, 30 columns for another. Join them using two columns (like a customer number and state field), then report the summary by state and month. And for grins, the customer numbers all have 30 leading zeros.
This is about 2-3 minutes work in Excel, including the preservation of the leading zeros. Let me know how Google Sheets works out for you.
Ed Hansberry
commented
"The issue with Google Sheets is that..."
And the fact that compared to Excel, Google Sheets is not even as powerful as Microsoft Works was. And I used Google Sheets at my prior company for 3 years.
Ed Hansberry
commented
FWIW, I am not posting workarounds so MS doesn't have to fix it. I am posting workarounds so people can get their jobs done TODAY because whatever solution MS does evenutally come up with, it will change 20+ years of how Excel deals with some things, and in any event, I suspect MS will not even take changing how many digits Excel can handle (15) into consideration. As for the CSV stuff, yeah, it isn't ideal how MS handles it today.
So, use the workarounds provided for now until whatever John [MS XL] posted about that is under review has something done about it, or wait.
If I waited until everything was perfect to do my job I'd be fired on the spot. My whole job is workarounds. And I am thankful for them. Job security. :-)
Ed Hansberry
commented
@brent - PowerQuery is a great solution to this. But the expectation here is Excel to be a CSV file editor, which was never the intent.
I use PowerQuery all of the time with CSV files to read data into Excel, but I use Access if I want to control exactly how CSV file output is done.
Ed Hansberry
commented
" The big problem I have now is with account numbers that have a letter at the end, power query throws an error when trying to convert them to number format."
It is because that isn't a number. Use the Number.FromText function inside a Try/Otherwise command.
Ed Hansberry
commented
@zak - you should read up on the Excel calculation engine at http://www.decisionmodels.com/calcsecrets.htm. Being 16 bit, 32 bit, or 64 bit, has nothing to do with it. It has to do with how it was written and changing that would have massive MASSIVE issues to overcome. Not impossible, but not trivial.
If Excel suddenly changed and said "ok, every thing I import that I cannot handle, I need to convert to text" that would break MILLIONS of models that have been written in companies since the 80's. I have had this issue in the past and I wrote models around the issue using import templates early on, VBA import routines, and now PowerQuery. If Excel changed now, it would break what I had others have currently written. Or if you expect it to be converted and understand the 15 significant digit limitation and know it isn't material to your model, then those models would be trashed if those values suddenly came in as text.
That is the problem MS faces. They cannot just make a change to make it work for this without understanding how it will affect things that have been in existence for decades. It is like the 1900 date system in Excel where they screwed up and messed up the leap year when they programmed it. (or maybe it was Lotus that did that and Excel emulated it) If they just "fixed it" then people that had written functions to overcome the issue would suddenly find all of their calculations broken.
Excel isn't like apps on your iPhone that can just be changed on a whim. This is not a simple issue for MS to fix. I do hope they come up with a resolution, because there is definitely a small army of people that seem to want to put credit card numbers in Excel and have it magically figure out what to do with it.
Or, you could use PowerQuery in Excel and get around this. Or you could switch to Google Docs which doesn't have to worry about changing things like this, because no one with sophisticated models uses GDocs so no one would care if something changed.
Ed Hansberry
commented
@zak, you are comparing apples and catalytic converters. Notepad isn't doing anything. It is simply showing you what is in the file. Excel has to process numbers, and the calculation engine is only capable of handling 15 digits. To change that would be an insanely massive undertaking. Every computer program in the world the processes numbers has a limit on the significant digits it can handle. Solar calculators is usually 8. Excel is 15. Engineering software may be 30 or more. Software used in physics and math may be 100. Whatever it is, when you exceed that limit, the software will start turning digits to 0 on the right to preserve the numbers on the left.
If you want Excel to process it as text, then tell Excel it is text. Put it in quotes, or use PowerQuery to force it to text before loading it to a sheet or the data model.
Ed Hansberry
commented
@zak - Power Query eliminates the hassle as you only write the query one time. You don't go through that horrible import dialog box.
The problem is there is no standard for CSV files, but the rule of thumb is, numbers that should be treated as text should be enclosed with quotes. If you type 123456789123456789 into Excel, it will remove the last 5 digits because it simply cannot handle numbers with more than 15 significant digits.
I am not defending how Excel does it. I personally hate the autoformat garbage it does all throughout the app. Type "1 1/2" and excel assumes I want a fraction. It changes it to 1.5, then formats as a fraction. I have to undo that and force the cell as text format, or preceed with a ' character (single quote)
I am merely showing a way to avoid the issue. If you want more than 15 digits, you need to switch products. MS Access supports 28 significant digits for example if you make the field decimal.
And I just formatted a cell as text, put in a 21 char "number" into that cell, and saved as a CSV. Opened in Notepad and there was no truncation. Excel correctly saved all 21 digits to the file. It didn't put quotes around it though, so when I opened it up, it did truncate. When I imported via Power Query though, it kept all digits.
Ed Hansberry
commented
@Steve Burkhart, Excel's conversion to scientific notation isn't losing your data. Excel simply cannot handle more than 15 digits in a number. Period. If the file you are exporting is creating a CSV, you need to have it wrap the number in quotes. Excel will handle as text.
Or use Power Query built into Excel (2016) to do the import. There you can force the import as text and then when you load it to an Excel spreadsheet, it will come out as text and all your digits will be intact.
If you have 2013, you need to download the Power Query addin. I don't think it exists for 2010, and know it doesn't for 2007.
Ed Hansberry
commented
http://dailydoseofexcel.com/archives/2017/04/05/converting-numbers-to-text/ has info on how to put credit card numbers in Excel. The issue is Excel isn't broken, it just isn't being used properly. CC numbers aren't numbers, they should be strings, and should be entered as such. Excel cannot even handle a 16 digit number, which many CC #'s are.
Ed Hansberry
commented
Access can track it, but so can Excel. you just need to format the cell as TEXT before pasting the values in. That is what the TEXT format is for. Excel cannot handle a 22 digit number. Neither can Access for that matter. You'd need to format the table field as a TEXT/STRING field as well before adding the data in.
Ed Hansberry
commented
Roger, Excel doesn't destry numbers. It just converts the format, You can change the format back. That said, Excel only supports 15 digits. Entering 1234567890123456 will result in 1234567890123450 being in the cell.
For things like tracking numbers and IDs, those should be text anyway. In our company, anything that is any type of ID is always text, even zip codes, which are only 5 digits.
Ed Hansberry
supported this idea
·
-
405 votes95 comments · Excel for Windows (Desktop Application) » Formatting · Flag idea as inappropriate… · Admin →Ed Hansberry
supported this idea
·
-
2 votes0 comments · Excel for Windows (Desktop Application) » Data Import · Flag idea as inappropriate… · Admin →Ed Hansberry
shared this idea
·
-
7 votes1 comment · Excel for Windows (Desktop Application) » PivotTables and Power Pivot · Flag idea as inappropriate… · Admin →Ed Hansberry
supported this idea
·
-
3 votes1 comment · Excel for Windows (Desktop Application) » Data Import · Flag idea as inappropriate… · Admin →Ed Hansberry
commented
Same idea a the Power BI site for PQ - https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/20038996-have-a-visual-indicator-of-steps-that-are-folding
Ed Hansberry
shared this idea
·
-
213 votes22 comments · Excel for Windows (Desktop Application) » Data Import · Flag idea as inappropriate… · Admin →
Hi Joana & others,
Thanks for logging this suggestion. Yes, being able to protect your queries would be quite useful indeed for delivering solutions. We’ll prioritize this based on the interest, so if you’re reading this and haven’t voted as yet, please do so.
thanks
Ashvini Sharma
Lead Program Manager
ExcelEd Hansberry
commented
I half wonder if there is no impetus at MS to do this because if you do this in Power BI, the query is automatically hidden from the end user, and they get a $10 Power BI license.
Ed Hansberry
commented
@regan - that would work but has serious limitations as it becomes difficult to quicky modify/tweak the query, and prevents it from being used in a MERGE or APPEND without breaking query folding. No subsequent tasks in the query would fold either.
Ed Hansberry
commented
Ryan, that does work, but it also causes DAX to fail. So if your query is loaded to a table, that is fine,but if it feeds PowerPivot, it causes PowerPivot to stop working, or anything that relies on the Data Model, like the CUBE functions.
Ed Hansberry
supported this idea
·
-
501 votes251 comments · Excel for Windows (Desktop Application) » PivotTables and Power Pivot · Flag idea as inappropriate… · Admin →
Hi all,
I’m happy to announce that your input has had another direct impact on the product. In this case, a decision has been made to have Power Pivot be available in all Windows editions (“SKUs”) of Excel! This means the Business, Home, Standard, etc.. all of these will have Power Pivot. As your comments have indicated, Power Pivot has moved from targeting a specialized audience to generally useful capability for working with data in spreadsheets. As such, it makes sense to make this as broadly available as possible.
We have started rolling this change out with the April Current Channel updates (Builds 9330 and beyond). I’m also happy to announce that these SKU changes will be reflected on the upcoming 2019 version as well.
Thank you for pushing for this!
Ashvini Sharma
PM Manager
ExcelEd Hansberry
commented
Because @Mimi - this was a licensing decision that involved little to no coding and was just a decision to include it with all Office SKUs for Windows. The one you linked to is a massive code change to go back to the old way. I doubt they will revert that given they are now targeting the new Sets feature in Windows Redstone 5 due this year, and it won't work effectively with all documents in a single container. But they are looking at specific use cases as the post says at the top.
Ed Hansberry
commented
No exact date for Office 2019, but scheduled for the 2nd half of this year, which could be July 1 or December 31, or somewhere in between. MS hasn't finalized a date yet.
Ed Hansberry
commented
For those questioning the Insider track, you don't have to do that. LIke all features, MS is apparently rolling this out to Fast Insider first, then will move to Slow Insider when a bit more stable, then to normals when fully tested.
If you want it right now, then yes, you need to get Fast Insider, but understand you are getting a beta version of ALL of the office apps and there are bugs that may impact you. MS doesn't recommend using Fast Insider on production machines.
Ed Hansberry
commented
@mark - Office 365 for home is not licensed for commercial use. If your clients are individuals that just pay you to help with their PC needs, that is fine (though seems odd that kind of person would care about Power Pivot), but if your ciients are small businesses, they need to have an Office 365 business license, not home.
Ed Hansberry
supported this idea
·
Roy - I understand if you have two instances of Excel open then they will have separate undo stacks. But the transition from MDI to SDI did not change the fundamental way Excel works. Open 5 workbooks in Office 365, Excel 2016, or Excel 2019, and you only have one copy of Excel.exe running, unless you specifically caused a 2nd instance to launch (Alt-Click Excel icon).