web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

UTF-8 encoding in AIF schema

(0) ShareShare
ReportReport
Posted on by 150

Hi,

i am having outbound port the schema ii encoding=UTF-16, how to change encoding to UTF-8

Thanks

ram_ram

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    237,880 Most Valuable Professional on at

    Please don't change the topic of existing threads - create a new thread instead, use appropriate name, tags and so on. I moved this question from an another, already answered thread.

  • Martin Dráb Profile Picture
    237,880 Most Valuable Professional on at

    You would have to change how standard AX generates XML schemas. What's the problem you have with UTF-16?

  • Community Member Profile Picture
    on at

    UTF-8 is suppose to be subset of UTF-16, so having UTF-16 is not any issue

    what is the problem you are facing with UTF-16

    appreciated if you please explain your core issue.

  • Martin Dráb Profile Picture
    237,880 Most Valuable Professional on at

    UTF-8 is not a subset of UTF-16. They're two separate and incompatible (though convertible) encodings, both capable of encoding all Unicode characters. The main difference is in number of bytes used for encoding characters (e.g. UTF-8, unlike UTF-16, encodes certain characters with a single byte) and backward compatibility of UTF-8 with ASCII.

  • Community Member Profile Picture
    on at

    Main UTF-8 pros:

    •Basic ASCII characters like digits, Latin characters with no accents, etc. occupy one byte which is identical to US-ASCII representation. This way all US-ASCII strings become valid UTF-8, which provides decent backwards compatibility in many cases.

    •No null bytes, which allows to use null-terminated strings, this introduces a great deal of backwards compatibility too.

    Main UTF-8 cons:

    •Many common characters have different length, which slows indexing and calculating a string length terribly.

    Main UTF-16 pros:

    •Most reasonable characters, like Latin, Cyrillic, Chinese, Japanese can be represented with 2 bytes. Unless really exotic characters are needed, this means that the 16-bit subset of UTF-16 can be used as a fixed-length encoding, which speeds indexing.

    Main UTF-16 cons:

    •Lots of null bytes in US-ASCII strings, which means no null-terminated strings and a lot of wasted

  • Suggested answer
    Bashir Ahmad Profile Picture
    5,248 on at

    This may help to transform:

    technet.microsoft.com/.../hh352243.aspx

  • Community Member Profile Picture
    on at

    Hi,

    we have a custom service and the schema is in UTF-16 but our external system accepts only UTF-8 format. so is there a way to change schema with out using the transforms. we have UTF-8 as default and validation checked on the form. but still the schema is in UTF-16.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans