Friday, February 26, 2016

Dynamics AX Cloud POS (CPOS) activation error: DA1023 - Could not resolve employee's identity

When activating a new Dynamics AX Cloud POS (CPOS) instance, you may encounter the error 'DA1023 - Could not resolve employee's identity. Probably due to the user's external identity is not being mapped to an employee' (Figure 1 below). It fails on Setup 4 of 11. This can also occur in the Modern POS (MPOS).

You don't need to close out of the POS to resolve this issue. Once you fix the issue, which this blog post will explain, you can just hit retry. Assuming the data was pushed to the target retail channel, you should be good to go. 

You need to navigate to your worker in the AX application and edit the record. From there, hit the 'RETAIL' button in the navigation bar (Figure 2). There will be an option under the 'EXTERNAL IDENTITY' called 'Associate existing identity'. What this will do is link your login ID to an AX worker. In this case, I'm 000160. You will have to select the identity (Figure 3)

Once complete, run the 1060 job to push it to the retail channel (Figure 4). You should make it a best practice to click on the job's 'History' tab or navigate to the 'Download' form to make sure the data ran properly.

Navigate back to your 'Activate [Modern/Cloud] POS' screen and click 'Retry'. It should activate successfully as long as you have no other issues!

Figure 1- The error
Figure 2 - The 'Associate existing identity' option on the worker

Figure 3 - Associating the existing identity to a worker

Figure 4 - Run the 1060 retail job


  1. Interesting approach towards this. Wondering what you think of its implication on society as a whole though? Sometimes people get a little upset with global expansion. Ill check back to see what you have to say.
    Eloquent and concise. Like it.

  2. This comment has been removed by the author.

  3. This comment has been removed by the author.

  4. Hi,

    I'm using virtual machine(update 5, release by MS yesterday, March 29th 2017) however, am unable to associate existing identity to worker(as referred to figure 2 in this blog), it ends up saying service is not available. I donot see any filtered record, and when i press OK button, it says UPN is assigned to worker XXXXXX(some other worker).

    Have visited few other blogs which suggest about a trick to handle this, by selecting search by email id as the filtering criteria, however that does not work either for me.

    Is there a way to configure this, as its really a big pain to go through this.

    Any help or suggestions would be highly appreciable.


  5. @nishigandha yadav i have the same problem any idea how to resolve this?

  6. Hi guys! Thank you that you wrote a lot interesting information about microsoft dynamics ax partner and showing how to describing a problem with SQL Server! It’s very helping me, because I'm a beginner :) and it was very interesting for me.