1,260
Hi,
When I try to import a couple of items I get the following error:
I then followed the blog, which had the same issue. But later, when I validate the target entity I get the error:
and when I click "modify target mapping" to try to see what is currently set up, I get a different error:
The target entity seems broken still. I also get errors when trying to open the log:
*This post is locked for comments
Hello Everybody,
This worked for me.
Hope this helps.
- Mohammed
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 !
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.
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.
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.
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?
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.
Andre,
How did happened though? Like all of a sudden?
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.
#1
André Arnaud de Cal...
291,622
Super User 2024 Season 2
#2
Martin Dráb
230,354
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
