@Keith Dunlop -
Instead of using the custom format dd/MM/yyyy, please try using DD/MM/YYYY and validate. Let me know if this helps achieve your requirement.
dd/MM/yyyy
DD/MM/YYYY
Hope this helps!
@Keith Dunlop - Welcome to the Oracle Analytics Community!
Please try the following steps and let us know if it helps resolve the issue:
Refer to the screenshot below for guidance on where to locate this setting.
We encourage you to continue using the community forum, and feel free to reach out to us for any further assistance here.
Cheers Sumanth …
Thank you for your feedback & input .. Much appreciated.
Auto
This does address issue as Date data is not corrupted eg FIXE2LENGT02ATE
I am looking to format the output to dd/MM/yyyy
2.Once confirmed that it works correctly with the Auto format, switch back to the Custom format and check if the issue persists.
Custom
When I switch back to Custom and change the format to dd/MM/yyyy .
Date data is corrupted eg FIXE2LENGT02ATE
😀
That worked -
What the difference in using DD/MM/YYYY over dd/MM/yyyy?
Looking at your screen shot example image.png - The Auto default to MM/dd/yyyy h:mm:ss
What is reason behind having format value in lower case as value produced is a date - no chars to be uppercase
Thank you for your input .. Much appreciated.
Kd#
@Keith Dunlop - This suggestion was based on the SQL format standards recommended in the Oracle Database documentation, which specifies the use of uppercase format elements (e.g., DD/MM/YYYY).
Reference: https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/Format-Models.html#GUID-096CA64F-1DA3-4C49-A18B-ECC7518EE56C
This approach has been internally tested, validated, and is the recommended best practice.
It’s a minor change with no drawbacks, and ensures consistency and correct interpretation of date values across Oracle tools.
Hi @Sumanth V -Oracle We are facing the issue with csv export format of OAS DV workbook with the date column. We have changed the format to MM/dd/YYYY but in export we are getting date time. is it a bug? or do we have any workaround to fix it.
Regards
Sateesh