http://www.fourone.se/blog/2010/04/09/no-valid-document-identified-from-the-entity-key/ Dynamics AX development blog Thu, 09 Feb 2012 18:08:26 +0000 http://wordpress.org/?v=2.3.1 http://www.fourone.se/blog/2010/04/09/no-valid-document-identified-from-the-entity-key/#comment-11696 väinö Tue, 13 Apr 2010 06:21:02 +0000 http://www.fourone.se/blog/2010/04/09/no-valid-document-identified-from-the-entity-key/#comment-11696 At least in AX4, the error can also occur if record has been modified or deleted while the message is still in the AIF queue. That is, before the AIF batch job has processed the message from the queue. At least in AX4, the error can also occur if record has been modified or deleted while the message is still in the AIF queue. That is, before the AIF batch job has processed the message from the queue.

]]> http://www.fourone.se/blog/2010/04/09/no-valid-document-identified-from-the-entity-key/#comment-11685 Tue Mon, 12 Apr 2010 12:50:07 +0000 http://www.fourone.se/blog/2010/04/09/no-valid-document-identified-from-the-entity-key/#comment-11685 Hi, I had a similar problem. All AIF messages are being tested just before the serialization occurs. One of the tests checks wheter the source data still exists. To perfom this test AIF make a lookup based on the primary key index. If however one of the fields is a datetime you might experience this error as Ax sometimes stamps values in the milisecond part of the field. This (full) value however is not visible from the ax client, only from sql. I suspect a kernel error. Hi, I had a similar problem. All AIF messages are being tested just before the serialization occurs. One of the tests checks wheter the source data still exists. To perfom this test AIF make a lookup based on the primary key index. If however one of the fields is a datetime you might experience this error as Ax sometimes stamps values in the milisecond part of the field. This (full) value however is not visible from the ax client, only from sql. I suspect a kernel error.

]]>