Oracle Exalytics and OBIEE 220.127.116.11.X Analysis Does Not Retain Custom Date Format (YYYYMMDD) When Exported To Excel Or Comma Separated Values (CSV)
(Doc ID 1565415.1)
Last updated on FEBRUARY 11, 2020
Applies to:Business Intelligence Suite Enterprise Edition - Version 18.104.22.168.5 to 22.214.171.124.12 [Release 11g]
Oracle Exalytics Software - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Created an Oracle Business Intelligence Enterprise Edition (OBIEE) analysis in OBIEE version 188.8.131.52.5.
Edited "Order Date" column properties in OBIEE and checked "Override Default Data Format".
Set Date format to use 'YYYYDDMM' format and saved analysis.
When running this report in OBIEE, the "order date" column displays the dates as expected (i.e. 20131220, 20130503, etc.).
If the Analysis is exported to Excel 2010 or to CSV format, the date format is not preserved.
Instead of seeing the formatted date, the CSV file shows "############" and Excel 2010 also shows "################".
If the Excel cell is clicked, the expected date will display in the formula bar (fx) area at the top of the worksheet, but it does not show the expected value in the actual cell.
Excel and OBIEE language settings are both set to English (US) as default.
The format on the Excel export is preserved if default date format is used.
This problem only happens when the custom date format is used - i.e. override default format; and when exported to CSV or Excel.
This problem also occurs in other versions of the OBIEE 184.108.40.206 product family (i.e. 220.127.116.11.8 and 18.104.22.168.10).
This problem may occur on standalone OBIEE environments and/or Oracle Exalytics servers that also include OBIEE.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document