I have a Excel file (.xlsm type) contains lot of Charts. After switch to Excel 2016, certain charts not showing Label correctly (axis-x).
Eg. It suppose showing WK10'17, WK11'17, WK12'17,...
but it showing 1,2,3,4,....
1) I tried to reselect the data, then the label showing correctly, but after save and reopen, it become 1,2,3,4.... again
2) also tried delete the existing chart, and create a new one in Excel 2010 & 2016, problem not solve.
3) Axis Type have been set as Text
Is this a bug in Excel 2016 ? Did anyone have a solution for this ?
Below Chart showing 1,2,3,4,..., which is wrong.
Below chart is showing correctly.
Below are my table look like
1st Experiment:
Firstly, I create a whole new file in Excel 2016. Then do below step:
- Create 4 Indicators for performance review, with dummy data
- Create new chart and format it
- Create simple VBA code to hide everything, and only show related Indicator that selected
Everything work just fine, even switching around the indicator many times.
Later, Close it and reopen, 3 out of 4 charts having Axis-x label became 1,2,3,...
2nd Experiment:
I created Whole new file in Excel 2010, with 4 indicators and same VBA code.
Then Close and reopen, Axis-x format remain Perfectly good.
Transfer the file into Excel 2016 machine. Close and reopen, the Axis-x became 1,2,3....
*** Current Excel Version 1705 (Build 8201.2075)
*** Attach with these experiment files
4Q Demo.zip
Appreciate, who got interested into this issue, have a look on my file.
Share with me, if you do have any solution for that. Thanks
I found out as long as the Chart is not hide, then the axis-x will remain correctly. But this do not really help, when hiding additional chart is a must.
Another temporary workaround method is :
1) moving the data table to another worksheet.
2) Then the set the Chart's data range to another worksheet (Cannot be the same worksheet with Chart).
That will work perfectly, now can hide the chart while maintain axis-x correctly.
**** Only drawback, table have to move or duplicate into another worksheet
**** Probably Microsoft will solve this after Version 1705 (Build 8201.2075)
Related
I've found out a compatibility issue, trying to save .xlsx file with Epplus.Core library.
If I open generated file in Excel 2016, everything is perfect, but if I use macOs or iOs Numbers application, then all the charts dissapear.
I get an error:
"Charts of unsupported type or size were either imported as an image or removed".
Also want to notice, that during tests sometimes charts appeared in file, but axis had wrong scale (values were about 4kk, but axis max limit was just 4).
It's very important for me to create file, that could be read correctly in both Excel and Numbers applications.
I've thought about exporting worksheet to .pdf, but I have several worksheets, and it would be problem to export two files (one .xlsx with data and another one .pdf with charts) in one moment.
Is there any other solution for this issue?
Finally the problem was in naming of worksheet with chart's datatable.
It should be no spaces in worksheet name, then Apple Numbers successfully display all the charts.
Also chart with type = eChartType.BarClustered can become a problem.
I don't know why, but Apple Numbers throw an error, if there is chart with this type on worksheet.
My employer has recently upgraded from
Excel 2013 (15.0.4805.1001)
MSO (15.0.4919.1002) 32-bit to Excel for Office 365 MSO (16.0.11328.20362) 32-bit
There are no active add-ins (other than referred to below when loaded).
An Excel add-in (xlam) that I have created no longer functions correctly.
The add-in works with an open workbook and formats a lot of 'raw' data as tables (listobjects) and creates a number of PivotTables and Charts in a dashboard-style layout. During the process some blank sheets are copied from the add-in to the open workbook, and renamed as required.
For the most part, everything works fine (pivots created, dashboard created). At the end of the process I create an index sheet by copying a blank sheet from the add-in, and re-naming it (as ...Index). This is where things go wrong. Excel just seemed to 'hang'. On investigation I discovered that the sheet was not being renamed (so further processing stopped).
Delving into this further with error-trapping turned off, if I try to rename the sheet using the immediate window, I get
run-time error 7 Out of Memory
Further, if I manually rename the sheet (Excel interface) and then set the code running from that point, I've discovered that I can't use the CurrentRegion property (some sorting is done on the newly inserted sheet). Any attempt to use CurrentRegion results in
Unable to get the CurrentRegion property of the Range Class
This also applies to using the immediate window on ANY open workbook (e.g. ?Activesheet.range("A1").CurrentRegion.Rows.Count)
These errors persist during the current session of Excel (that is, I can create a blank workbook and try to rename a sheet using VBA but get an error; manually renaming a tab is OK). If I restart Excel everything is fine.
I require to use some global/public variables but (given that everything worked in Excel 2013) can't see that these would be the problem.
Any ideas?
After a further couple of hours looking into this, I established that the error was related in some way to a module which added slicers to the dashboard. The slicers were, in fact added (and stepping through the code no errors were generated).
Adding the slicers in a slightly different fashion appears to have got around the problem, although I am still none the wiser as to why it actually occurred in the first place (the original code for the slicers worked fine in Excel 2013).
I distribute Excel spreadsheets as Balanced Scorecard tools to all my clients. I have just received once back where a sheet, one of many in the workbook, has been changed:
All hidden rows and columns have been unhidden
Sheet protected has been set to not protected
Most of the formatting has been lost
Functional images on row one have been removed
Set column widths have been reset to default
Grids are turned on
The following two images show what the sheet should look line and what has happened.
Before:
After:
The customer runs Office 2016 on a Windows 10 PC.
Has anyone seen this happen before?
Can anyone tell me what causes this to happen?
I have a following excel 2007 template (.xlsx):
I have set up an SSIS process to copy that template and populate the first two columns with data as the file will be printed and then signed by order recipients. Everything is going well except for one thing - after the process populates the template with data, the cells don't retain their size - making signature cells too small.
Any ideas on how to force excel to keep the cell heights ?
One idea would be to create a macro that runs when the workbook is opened and it sets the row height using the Range.RowHeight property, here:
https://msdn.microsoft.com/en-us/library/office/ff193926.aspx
If anyone ever has a similar issue, I managed to find a workaround. Instead of using SSIS I'm using SSRS where I keep the cell height by adding an "invisible (white text on white background) column at the end. I set up an SSRS subscription to automatically export the data and send as an Excel.
I have a Excel Workbook in which I have created an analysis using Datatables. For some reason each time I open the workbook, the formulas that reference the Datatable turn into #Name erorrs.
The first time I opened it, I thought I had simply made a typo and needed to reenter the formula. I did that and saved the file. On opening it two minutes later.... same error!
The error is only for two referenced columns in the datatable. Other columns from the same table reference fine, without error!
Here a sample of what the error looks like:
=SUMIFS(tblDB #REF!,tblDB[AWGW 2012],$B$3,tblDB[NWGW 2012],$B13)
The file (saved as an .xlsm) contains the following, none of which are used or touched by the formulas with the error:
Pivot Tables
VBA Code (none are event based... regular subs that need to be manually started only)
Other Datatables
I have tested on the the following Systems:
Excel 2010 (32bit) and Windows XP
Excel 2010 (64bit) and Windows 7
Does anyone have any idea why this happens?