Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 240 Big Data Appliance
- 1.9K Data Science
- 450.4K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187.1K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 443 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Oracle Apex 20.2 CSV and Excel issues with embedded ">" and "≤" characters

Hi forum,
Oracle 19c, Apex 20.2
We have a simple interactive report where two of the columns have embedded ">" and "≤" characters in the output. The CSV export replaces the "≤" with simply "=" and the ">" is shown okay. The Excel export reports a problem when opening up Excel to display the file. Removing the column with the embedded ">" makes the problem go away. Clicking "Yes" on the recovery does however open the report with the correct data. Here's a snippet of the IR:
The Excel problem shown is:
And the CSV (which also shows a problem when Excel tries to open it) looks like this in Notepad++:
Has anyone seen this behavior? I saw a previous post about setting the Automatic CSV Encoding "on" which we have by default:
Any help would be appreciated!
Cheers,
Barry