Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
When the user clicks “Add Dossiers” to create dossier which its DSN-less DB role uses Strategy PostgreSQL ODBC driver to retrieve data from PostgreSQL warehouse in connect live mode or in memory mode on Workstation.
Then save the dossier to the Linux I-server connected Workstation.
Double click to view the dossier, the data should be fine but when the user edit the dataset->edit the table-> re-connect the DB role, will get below incorrect namespace list.
Since Strategy 11.0 has newly shipped native PostgreSQL ODBC driver, there are two PostgreSQL ODBC driver for user options: Strategy PostgreSQL ODBC Driver and Native PostgreSQL Unicode(x64) ODBC Driver. Strategy shows the native PostgreSQL Unicode(x64) ODBC driver as the primary one on Data Import interface.
Therefore, when you upload a MSTR file using the secondary Strategy PostgreSQL ODBC Driver DSN-less connection to Linux I-Server.
The connection will be converted to fit in the primary ODBC driver which is PostgreSQL Unicode(x64) connection string.
While the two ODBC drivers have different character set behaviors.
From Developer the user can check the DB role character set by click the DB role->Modify the Database connection->Advanced tab.
The DB role created with Strategy PostgreSQL ODBC Driver should display as below:
The DB role created with Native PostgreSQL Unicode(x64) ODBC Driver should display as below:
Currently this issue is being reviewed by Strategy Technology team for a potential code fix on an upcoming Strategy release.
Edit the DB role and click the “Save” button without changing anything in DB role configuration. Or the administrator can modify the character set encoding for Unix drivers option to “Non UTF-8” following the Native PostgreSQL Unicode(x64) ODBC Driver rules in Developer.
KB442379
