Hello,
I noticed a little annoying issue about the encoding of files of Member List or Rule in 11.1.2.4+. Those problem seems to be related to VB Engine used by HFM.
If I try to update Member List or Rule by uploading the file encoded in UTF-16, no problem, all special characters are correctly encoded, and the file extracted displays everything correctly.
But If I try to upload Member List or Rule in another encoding of UTF-16, for example Windows-1252 (CP1252), when I try to extract the newly updated file, all special characters are broken. I'm pretty sure it's because of some wrong usage of VB dll msxml, which does UTF-16 encode by default, even my file is not UTF-16 encoded, which is an issue when the file is not UTF-16 encoded. I'm sure about this automatic conversion because I checked the hfm_binary table and I could see the BLOB, and if it's not in UTF-16, the extracted file is broken.
Unfortunately, even the source is in UTF-16, the encoding of the file returned by HFM is not in UTF-16 but in Windows-1252. So the workaround is to think about converting to UTF-16 before reuploading the file.
Does someone know either how to edit the encoding of the file returned by HFM or how to avoid the VB engine converting to UTF-16 whatever the encoding of the file being uploaded?
Please find below a summary of the workflow related in this post.
