I am generally getting such queries that We have a Planning application that contains special accented characters that are not supported as part of the West European character set. When creating the data source for this application, we forgot to check the “Unicode” option for the Essbase application. This means that some of the aliases in the Essbase outline contain “?” instead of the correct accented characters.
How can we convert the Essbase part of our Planning application to unicode mode now that it has already been created in Essbase?
It is possible to enable unicode support for the application in Essbase, and for the Planning datasource, and the change should take effect immediately, with no need to re-load data or recreate the application.
First, back up your Essbase data and your Planning relational database, just in case.
1. Log into the EAS console
2. Right-click on your Essbase server > Edit > Properties > Security tab
3. Confirm that the “Permission to create Unicode-mode application” checkbox is checked
4. Still in EAS, right-click on the Planning application in the list of applications > Edit properties
5. On the General tab, check the “Unicode mode” checkbox
6. Click “Apply”. You are warned that this change is non-reversible.
7. Edit the datasource for your Planning application
8. Check the “Unicode mode” checkbox (and re-enter passwords). Click “Finish”.
9. Log into your Planning application and perform a refresh
You should now be able to refresh member names and aliases containing characters not supported by the basic Latin1 ESSLANG (e.g. ž).