Hello! We discovered some core_company records imported through the MID Server that have garbled characters (Shift-JIS encoding) in their names, which are originally in Japanese.
When we restore these garbled records, we usually find that a separate record with the same name already exists. As a result, we end up deleting the garbled records and using the existing records instead.
What could be the possible cause(s) of this issue? Could this be related to character encoding or the way the MID Server handles the imported data?
I apologize if this is a basic question, as I don't have much experience with MID Servers. Any advice or suggestions on where we should investigate would be greatly appreciated.
#mid-server #itom #import #discovery
