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) / The document hash does...
Microsoft Dynamics AX (Archived)

The document hash does not match the hash in the XML.

(0) ShareShare
ReportReport
Posted on by alexd 457

Hello all,

I am trying to setup the HcmWorkerImportService in conjunction with the Excel Add-In so that our HR people are able to import/export and update HR related information.

So far I've been able to get excel to fetch information, but if change a value, such as the initials for example, I get the following error:

"The document hash does not match the hash in the XML. The document may have been changed since last readDocument Worker could not be updated. Error details: The document hash does not match the hash in the XML. The document may have been changed since last read"

I am using the Add Data option on the add-in.

If I use the Add Tables option, available only for sysadmins, I am able to update the field with no errors.

Any thoughts?

*This post is locked for comments

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

    The simplest explanation is that the message is correct and the data changed in AX after you read the record and before you updated it. AX has to make sure that you don't intentionally overwrite changes in AX.

    You should investigate this possibility before looking for other problems.

  • alexd Profile Picture
    alexd 457 on at

    Hi Martin,

    That's what I thought at first but then I made sure I was the only one working in AX at the time and I refreshed the table immediately before updating and still got the same message.

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

    Then I suggest you compare the hash returned by the read operation and the one send by the update. If they're the same, some data must have changed in AX. If they're different, Excel sends an incorrect hash for some reason.

    It will help us to focus on the right component.

  • Community Member Profile Picture
    Community Member on at

    Hi, were you able to figure out what the problem was?  I had this problem too that went on for 2 weeks.  No one was updating AX, but the document hash from last read was getting rejected when sending the update.   After 2 weeks, it just started working again, and to my surprise, it worked on exactly the same document hash that was failing for a while.

    Marites

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