KB426490: Reports with the results containing data as both emoticon and accent characters from Amazon RedShift can't be executed succesfully in MicroStrategy 10.3

When a report contains the results having both emoticon(i.g. '&##128513;') and accent characters(i.g. 'é') which were retrieved from Amazon RedShift, it fails to be run.
The scenario is that accents such as é can work with Non UTF-8 and fail with UTF-8 mode in DBI (error message would be UTF8ToWideChar). While on the other hand, emoji characters like &##128513; can work with UTF-8 but fail with non UTF-8(error message :WideCharToUTF8).
Therefore when results contain both emoji &##128513; and accent é, the report cannot be executed.
STEP TO REPRODUCE:

• Create a DBI for Amazon RedShift, set character coding as UTF-8.
• Create a table with a field "name" in varchar in RedShift.
• Insert 'é' into the "name" via Aginity workbench for RedShift (a certified native tool for RedShift)
• Build attribute for the field and then create a report for it.
• Run report and error occurs as below. If users exclude 'é' from the name, the error is gone.
  

• Update name value back with 'é'. Change DBI character coding as non UTF-8. Restart the intelligence server and re-execute report. The error is gone.
• Insert emoji '&##128513;' into "name" via Aginity workbench for RedShift.(note, character coding now is non UTF-8)
• Re-execute the report and the error occurs. If users exclude emoticon '&##128513;', the error is gone.
  

CAUSE
Accent characters should be recognized from non-utf8, but the emojis like &##128513;, belong to Surrogate Pair of UTF-16 which belongs to Supplementary Planes that are not supported for convention in Strategy.
ACTION
This is fixed in 10.4.4 and 10.8. Upgrade to take advantage of the fix.