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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / DIXF services are abo...
Microsoft Dynamics AX (Archived)

DIXF services are aborted when we import data saved in the UnicodeBE(Big Endian) format

(0) ShareShare
ReportReport
Posted on by Community Member

Hi all.

we working on tests to import data saved in the UTF-8 format into DynamicsAX.
We can properly import data saved in the Unicode Little Endian format.
But when we import data saved in the UnicodeBE(Bif Endian) format using DIXF,errors occur and DIXF services are aborted.
Though we don't currently assume importing data saved in the UnicodeBE format,we are afraid that,if users inappropriately import such data,we have to troubleshoot them.
Could you tell us possible causes and workarounds?

About settings:
1.[Source data formats]- Type : "File"
2.[Regional settings]- Codepage : "65001",whitch stands for "Unicode(UTF-8)"
3.[Regional settings]- Unicode : not selected
4.[Regional settings]- Language Locale : "JA"

Thanks.

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,037 Super User 2025 Season 2 on at

    Hi Yuko,

    This question is different compared to your earlier question? https://community.dynamics.com/ax/f/33/t/197403

    You also tried to select Unicode as mentioned by Martin? If there is no setting here which would help you, you can create a support ticket for Microsoft Support. 

  • Community Member Profile Picture
    Community Member on at

    This question is associated with our other one, but not the same.

    Would you check our additional comment to the one.

    What we would like to mention here is the behavior that DIXF services are aborted

    when files output in the UTF-16 Big Endian (CODEPAGE:1201) are imported in the UTF-8 (CODEPAGE:65001)format.

    The same behavior is observed eith files including only ASCII characters.

    We think there are hardly any cases where UTF-16BE files are imported in the UTF-8LEformat,

    but have to assume every possible behavior caused by enduser's unexpectted operations.

    We might feel it is not a serious problem when such file importing resulted in error-mesage indication.

    But we think this behavior may seriously affect systemoperations because service monitoring/restooration

    syould be taken into consideration.

    This is reason we ask whether there are any workarouds.

    We are planning to consult the MS support as you kindly instructed to do so.

    Thank you for your instruction.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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