Known Issues

• When updating from version 1.2.x (or lower) to the upcoming version 1.4.x (or newer), firstly you must install 1.3.x and start your reports and save them as 1.3.x format, to migrate them to the new internal format. Then you can upgrade to the preferred version.
  
  
• Data SeriesWidth in the Data Series Style Editor is, at the moment, only possible for bar/column charts. Please use the parameter Bar Width in the properties for waterfall, stacked and offset bar charts. Also the Width of the Data Types cannot be used for waterfall and stacked bar charts.
  
  
• Series Labels Right/Bottom of the waterfall and the stacked bar chart are not always drawn correctly.

• For technical reasons, the Title field known from graphomate charts for Lumira Designer is not available in Excel. Also, the Lumira Designer functions Manual Data Input, CSS Export for Data types, PNG-Export as well as Tooltips are not supported in Excel.

• If two different workbooks containing identically named charts are opened, an error message is displayed. The duplicated chart names have to be changed in either one workbook, so both can be displayed at the same time.
  
  
• If the cell content starts with something that usually introduces a formula in Excel, then the input must be preceded by a single apostrophe ' as a string. This behaviour occurs when the Property Cellbinding is used to define the Extended Number Format for example.
  
  
• If graphomate charts for Excel are inserted as OLE objects into other MS Office applications, these can only be refreshed if the original chart has already been opened in Excel. If PowerPoint respectively Word are opened first, the automated startup of the Excel workbook will result in a row of error messages, as in this case, a connection to the graphomate add-in cannot be established.
  
  
• Chart looses connection to the property sheet after reopening.
  
  
• Guideline to umlauts, special characters and blank spaces In general umlauts, special characters and blank spaces Umlauts are percent encoded for technical reasons in the Additional Properties Sheet (see: http://en.wikipedia.org/wiki/Percent-encoding).

Example: Nestlé - Development of sales in % compared to the previous year becomes: Nestl%C3%A9%20%20Development%20of%20sales%20in%20%25%20compared%20to%20the%20previous%20year 

This makes it necessary to percent encode string values even while transferring them from the scripting language or Basic Properties Sheet. (On the Internet there are many free tools for en-/decoding, for example: http://www.url-encode-decode.com/.) Lots of tools to do this are available on the internet, e.g. http://www.url-encoder.de.