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) / Entity query version i...
Microsoft Dynamics AX (Archived)

Entity query version is not matching with AOT version

(0) ShareShare
ReportReport
Posted on by Daljit Kaur Rahsi 1,260

Hi,

When I try to import a couple of items I get the following error:

Query-version1.jpg

I then followed the blog, which had the same issue. But later, when I validate the target entity I get the error:

Query-version2.jpg

and when I click "modify target mapping" to try to see what is currently set up, I get a different error:

Query-version3.jpg

The target entity seems broken still. I also get errors when trying to open the log:

Query-version4.jpg

*This post is locked for comments

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

    Hi D_Meethu,

    This error comes if the  query object has been changed and not updated correctly in the DIXF target meta data. You can solve the problem by or Regenerating the field mapping from scratch or delete the target entity and recreate this one manually. You have to write down the values used on for staging table, target query and the class to verify if recreating the entity is using the correct AOT objects.

  • Daljit Kaur Rahsi Profile Picture
    Daljit Kaur Rahsi 1,260 on at

    Andre,

    How did happened though? Like all of a sudden?

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

    Hi D_Meethu,

    There is an internal version number of the query stored in the AOT. This changes every time the query is changed and saved in the development environment. A change might be the fact that new fields or another data source was added. In that case the meta data stored for the field mapping between staging and target is outdated and needs to be updated. For that purpose DIXF has a check on the version number of the query.

  • Daljit Kaur Rahsi Profile Picture
    Daljit Kaur Rahsi 1,260 on at

    Andre,

    The target entity 'items' is one that comes with AX out of the box. Is there a way to just restore it to the original?

    I am mapping only the three fields in the processing group so recreating that part is not a problem.

    But is there any way to restore it to the original?

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

    Hi D_Meethu,

    What exactly do you mean with "restore it to the original"?  It would be possible to regenerate the staging to target mapping. This is what I mentioned above. This is just meta data. The entities (and related queries) are part of the application. The meta data is built when you open the target entities the first time. If you have an upgraded environment, probably also the query has been updated and thus requires regeneration of the meta data.

  • Daljit Kaur Rahsi Profile Picture
    Daljit Kaur Rahsi 1,260 on at

    Andre,

    Actually what happened was, one of the developer promoted his xpo's in the live environment. But for some reason it did not work in the live whereas it worked in the test environment.

    So the whole maintenance window was rolled back to the date prior to when he had imported his xpo's.

    The DIXF for items worked fine but as we rolled back or xpo's was added it started to give the errors.

    Is this reason why I am getting the errors because of the rolled back?

    "Restore it to the original" meaning can I have the DIXF for items similar to the one I had working before the xpo's, although we had rolled back.

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

    Hi D_Meethu,

    It can be indeed caused by promoting and reverting the XPO's. Were you able to re-generate the mappings? This should solve your issue.

  • Verified answer
    Daljit Kaur Rahsi Profile Picture
    Daljit Kaur Rahsi 1,260 on at

    Andre,

    At the time of upgrade and rollback the DIXF service was not restarted along with AOS services. I restarted the DIXF and it started to work. :)

    Thank you so much for you support :)

    Happy Wednesday !

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hello Everybody,

    This worked for me.

    1. Delete any dependent processing groups.
    2. Delete target entity.
    3. Recreate target entity from updated query.
    4. Validate.

    Hope this helps.

    - Mohammed

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
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
Ali Zaidi Profile Picture

Ali Zaidi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans