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) / [AX 2012} Customeraddr...
Microsoft Dynamics AX (Archived)

[AX 2012} Customeraddress rec ID (Connector for Microsoft Dynamics)

(0) ShareShare
ReportReport
Posted on by Community Member

I'm integrating MS CRM 2011 with AX 2012 R2 using Connector for Microsoft Dynamics.

Address mapping on account and contact do not make any sense whatsoever.

It states that "All addresses/Dynamics Integration Key" is mapped to the source field of "Organization\Item\Postal Address View\Item\Recid" but this is not the case. The ID's that are saved in CRM database are not the same as the Rec ID's in AX for that address.

This is causing issues, only first adress from AX is getting across to CRM and when you try to add a new address in AX the Connector throws exceptions because it cant find a customeraddress with id= ___________ because it does not exist.

You can add multiple addresses in CRM that are getting across to AX just fine. Its the AX -> CRM direction that is failing

How are addresses supposed to be mapped from AX 2012 to CRM 2011 in Connector for Microsoft Dynamics?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    When new addresses are created in AX, if they are not the primary address, then they will either become the secondary address in CRM (if it is the second address in the AX address collection) or it will appear in the more addresses collection in CRM.  The Dynamics Integration Key is a custom field that is added by the Connector's CRM solution in CRM and by default it is mapped to the address's RecId in AX.  Adding an address in AX normally is not enough to get the integration to flow however, normally you need to also change a field on the parent entity to get the address to move.  Have you contacted Microsoft Support on this issue?

  • Community Member Profile Picture
    Community Member on at

    We did open a support ticket for this. The main issues are with address number 2 in CRM, so we solved most part of this by disabling that.

    We still feel the Connector is a bit wonky regarding addresses though. Sometimes it writes the changes to the other system, sometimes it doesn't. (sometimes it even says "1 written" but no change is actually made).

    Like you say "Adding an address in AX normally is not enough to get the integration to flow however, normally you need to also change a field on the parent entity to get the address to move."  The keyword here is normally, because sometimes when we add a new address this is written to the other system, sometimes nothing happens until we do another change on the record. 

    In my world, it is either working or it is not. I don't understand how it is working only sometimes.

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