Connector for Microsoft Dynamics V2 RU1 released today! This release includes enhanced integration options and maps, and also resolves some of the key issues that you might be facing with your V2 deployments. Additional features and updates are listed later in this post. Stay tuned to this blog for upcoming videos that detail the new features and functionality.
To download this release for your Microsoft Dynamics ERP system, go to PartnerSource:
Don’t have access to PartnerSource but would like to know more? Check out the User Guide for your ERP system and begin your installation preparation. I know, I know; reading documentation can be an arduous task. But you know what they say: an ounce of prevention is worth a pound of cure. So read the provided documentation to avoid the common mistakes and save yourself the support call.
In an upcoming post, we will explain the new features included in this release, but here is an overview of the feature list:
Features for Microsoft Dynamics GP
Features for Microsoft Dynamics NAV
Features for Microsoft Dynamics AX
Features for Microsoft Dynamics SL
WOW! I'm pretty impressed with all those mentioned fixes and improvements! Apperently need for update for all existing customers, even if they work with no issues.
Thanks for the good work guys!
AX could also need the global picklist for country entry, why is it only NAV getting this solution ?
Another thing that would be great is a defautl vendor map, in AX 2012 it's a pain getting this working right because of custom code on services etc. !!!
I have a customer, who has "CRM" Adapter Settings but not "CRM2011".
I already found that PickList Adapter with Counry Code anvailable only for CRM2011 Adapter.
Could you point what else from new version features list not available for old CRM Adapter Settings?
@Jack - Yes any ERP can take advantage of this new functionality, provided that they expose their country codes for integration, which NAV has with the hot fix listed above.
@Konstantin - in the above list of features, we tried to call out the ones that were specifi to CRM 2011 by listing CRM 2011 in the description, so if you see a feature that is listed as simply for CRM, then most likely it was added to the legacy adapter as well.
Thanks for the great Post.
I am facing problem while mapping Pricelist and pricelistItem entity in connector from Ax 2012 to CRM 2011 integration. The problem is, I can able to create Pricelist (header record) but not able to create corresponding PricelistItem(child record).Pls help me to solve this problem.. if required I will give you a brief explanation....
@Abbas ibu - the price list entries in CRM are created when the products are integrated. Are you using the default mapping templates?
When I use Bulk Submit in CRM, the Integration Key generated doesn't seem to be unique, i.e. it just uses the Contact's last name as the key instead of generating an auto numbers. Will this cause issue during the sync?
@Y Kang - this could cause an issue if you have Contacts with duplicate last names.
@thehetz - Are you able to confirm if the last name (unique ID) is still a known limitation with the latest V3 release? If so any thoughts on the roadmap for changing this unique identifier? Suffice to say we have quite a few folks with the same last name in our CRM as I'm expecting about 99% of CRM customers would have the same.
@Dillon Bailey - the latest version of the bulk submit workflow does set the Integration Key to be the contact's last name only. If the contacts are individually submitted then that attribute is set using our plugin logic which will ensure uniqueness.
I have created a service of entities which are 1:n relationship and it was working fine but recently i am receiving below error.
"A record level exception has occurred for record Error text : 'bde_pricedisctable' entity doesn't contain attribute with Name = 'bde_wi_fixedpricetableid'".
as this was working earlier why it stop working!!
please help as i have stuck on this.
@Subhash mahato - if this was working then I believe that it might be data related. Is it possible that someone created a record that does not have the proper relationship s defined or that the entity was modified in some way as to remove the relationship and now the object definition and map are not in sync with the Dynamics CRM metadata?