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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

DIXF Copy to Target does not work after AX Upgrade

(0) ShareShare
ReportReport
Posted on by 1,632

After upgrading AX 2012 from CU8 to CU13, the DIXF Copy to Target does not work.

DIXF copy to Staging works just fine.

Copy to Target only gives the following message:

Data written to target 'Inventory journal' ('0' records created, '0' records updated)

There are no customizations and this is true for all the Process entities.

There is no other information that I can find and I'm at a loss for what to look at next.  Any help is greatly appreciated.

*This post is locked for comments

I have the same question (0)
  • DynamicsAXExplorer Profile Picture
    431 on at

    With how many records are you inserting ? Did you try with single record? Did you check in Execution History, Error Log, InfoLog? If yes, can you provide me what errors its showing?

    Also check if your file has special Characters.

  • Suggested answer
    István Orosz Profile Picture
    2,137 on at

    +1 Crispin
    and you should check the staging error logs in the execution history please

  • FAC.Ansel Profile Picture
    1,632 on at

    I have tried with multiple records and a single record, all with the same results.  I have also tried to use the other DIXF uploads like Inventory Journals, BOM load, items, etc. and I get the EXACT SAME results.  All of these worked for 2 years before the upgrade happened this past week.  I have checked the Execution history, error log, and infolog.  The data loads successfully to Staging but when running the staging to target, the Error message is Always the same, for all uploads:

    Data written to target 'Inventory journal' ('0' records created, '0' records updated)

    Crispin, I will try to debug it.  Thanks for giving me the method as a starting point.

  • Suggested answer
    FAC.Ansel Profile Picture
    1,632 on at

    After a lot of digging, I found that a method in a lower level had the original code (before the upgrade) with no modifications.  My guess is that someone accidentally saved the code to the level and didn't know it, as nothing was modified from the original code.  I deleted the method in that layer, compiled, and now it all works.  

    Thanks everyone for the suggestions, hopefully this helps someone else out there.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
Basit Profile Picture

Basit 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans