Customizing a Microsoft Dynamics AX 2012 and Microsoft Dynamics CRM 2011 Integration


If you need to expose a custom table in Microsoft Dynamics AX 2012 for integration to a custom entity in Microsoft Dynamics CRM 2011, then this post is for you!  Let's say that you will be creating a custom entity in Microsoft Dynamics CRM 2011 and that entity really doesn't integrate to one of the out of the box tables in Microsoft Dynamics AX 2012 or that you would like to integrate to a staging table in Microsoft Dynamics AX 2012 and then have your custom Microsoft Dynamics AX 2012 code pick up the data from that table and process it.  For the purposes of this post, we will be creating a "Feature Request" entity in both systems for tracking feature requests from customers. 

This post will outline how to create the table in Microsoft Dynamics AX 2012, how to create the entity in Microsoft Dynamics CRM 2011, how to expose both of those customizations to Connector for Microsoft Dynamics, and finally how to map them together.  This post also assumes that you would like these records to be bi-directionally synced, that is creates and updates in either system will be reflected in the other integrated system.  It should be noted that this post does NOT describe how to support the deletion of custom records in either system.  Currently the integration of deletes for custom records or entities in either Microsoft Dynamics CRM  or Microsoft Dynamics AX is not supported by Connector for Microsoft Dynamics.  If you have already created your custom Microsoft Dynamics AX 2012 artifacts as well as your Microsoft Dynamics CRM 2011 artifacts, then you can skip to this section of this post.

Prerequisites

This post assumes that you have the following set up and installation steps have been completed (more information on Connector for Microsoft Dynamics installation can be found in this post)

  1. Microsoft Dynamics CRM Online or Microsoft Dynamics CRM 2011 installed with Update Rollup 11 or above
  2. Microsoft Dynamics AX 2012 Cumulative Update 2 or Microsoft Dynamics AX 2012 R2 with change tracking enabled on the Microsoft Dynamics AX 2012 database
  3. Connector for Microsoft Dynamics with Microsoft Dynamics AX 2012 and Microsoft Dynamics CRM 2011 Adapters configured
  4. An Integration and site for a Microsoft Dynamics AX 2012 Company and a Microsoft Dynamics CRM 2011 Organization have been created

This post also assumes that you are using a user account (s) that can perform the following functions:

  1. Microsoft Dynamics CRM customization
  2. Microsoft Dynamics AX customization in the AOT
  3. Microsoft Dynamics AX AIF document service creation
  4. Microsoft Dynamics AX AIF Inbound Port creation and activation

And finally this post assumes that you are comfortable in performing customization actions in both Microsoft Dynamics CRM 2011 and Microsoft Dynamics AX 2012 including the following:

  1. Microsoft Dynamics AX custom table
  2. Microsoft Dynamics AX AIF Document Service creation
  3. Microsoft Dynamics AX custom queries
  4. Microsoft Dynamics CRM custom entities
  5. Microsoft Dynamics CRM solutions

 

Customizing Microsoft Dynamics AX to Support Bi-Directional Data Integration

Create Custom Components

 The first step in this guide to customize Microsoft Dynamics AX to support bi-directional data integration is to determine what data you want to integrate in Microsoft Dynamics AX. For the purpose of this guide we will be creating the following components:

 

Component

Name

Property

Property Value

Table

FeatureRequest

 

 

 

 

CreateRecIdIndex

Yes

 

 

PrimaryIndex

PrimaryIndex

 

 

ClusterIndex

PrimaryIndex

 

 

ModifiedDateTime

Yes

 

 

ModifiedBy

Yes

 

 

ModifiedTransactionId

Yes

 

 

CreatedDateTime

Yes

 

 

CreatedBy

Yes

 

 

CreatedTransactionId

Yes

 

 

 

 

Fields (FeatureRequest)

FeatureId

 

 

 

 

Type

String

 

 

Name

FeatureId

 

 

Label

Feature ID

 

 

Help Text

The ID of the Feature

 

 

Mandatory

Yes

 

 

StringSize

20

 

 

 

 

 

FeatureName

 

 

 

 

Type

String

 

 

Name

FeatureName

 

 

Label

Feature Name

 

 

Help Text

The Name of the Feature Being Requested

 

 

StringSize

50

 

 

 

 

 

RequestedDate

 

 

 

 

Type

Date

 

 

Name

RequestedDate

 

 

Label

Requested Date

 

 

Help Text

The Date The Feature Request Was Made

 

 

Mandatory

No

 

 

 

 

 

 

 

 

 

FeatureDescription

 

 

 

 

Type

String

 

 

Name

Feature Description

 

 

Help Text

The Description of the Feature Being Requested

 

 

Mandatory

No

 

 

StringSize

1000

 

 

 

 

 

DAXIntegrationId

 

 (Note that this exact casing is required)

 

 

Type

GUID

 

 

Name

DAXIntegrationId

 

 

Label

Dynamics AX Integration ID

 

 

Help Text

The ID Used for the Dynamics Connector AX Adapter

 

 

Mandatory

No

 

 

 

 

Index (FeatureRequest)

PrimaryIndex

 

 

 

 

Name

PrimaryIndex

 

 

AllowDuplicates

No

 

 

Enabled

Yes

 

 

AlternateKey

Yes

 

 

Fields

FeatureId

 

 

 

 

Methods (FeatureRequest)

insert

 

 

 

 

Name

insert

Event Handler Subscription (insert of FeatureRequest)

 

 

 

 

 

Name

DynConn_InsertHandler

 

 

CalledWhen

Pre

 

 

EventHandlerType

X++

 

 

Class

DynamicsConnector

 

 

Method

SetDAXIntegrationId

 

 

AOTlink

\Classes\DynamicsConnector\

SetDAXIntegrationId

 

 

 

 

Query

FeatureRequestQuery

 

 

 

 

Name

FeatureRequestQuery

 

 

Title

Feature Request Query

 

 

Description

Query For Feature Request Table

Data Sources (FeatureRequestQuery)

 

 

 

 

FeatureRequest_1

 

 

 

 

Name

FeatureRequest_1

 

 

Table

FeatureRequest

 

 

Update

Yes

 

 

 

 

Fields (FeatureRequest_1)

 

 

 

 

DAXIntegrationId

 

 

 

 

Table

FeatureRequest

 

FeatureDescription

 

 

 

 

Table

FeatureRequest

 

FeatureId

 

 

 

 

Table

FeatureRequest

 

FeatureName

 

 

 

 

Table

FeatureRequest

 

RequestedDate

 

 

 

 

Table

FeatureRequest

 

RecId

 

 

 

 

Table

FeatureRequest

 

Execute the AIF Document Service Wizard

 Execute the AIF Document Service Wizard to create a new Document Service. 

Query

FeatureRequestQuery

Document Identification

 

Document Name

FeatureRequestDocument

Document Label

FeatureRequest

Class Names

 

Service Class Name

FeatureRequestDocumentService

Document Object Class Name

FeatureRequestDocument

Axd Class Name

AxdFeatureRequestDocument

Service Operations

 

Create

True

Read

True

Update

True

Delete

True

Find

True

FindKeys

True

GetKeys

True

GetChangedKeys

True

AxBC Generation

 

Generate AxBC Classes

True

 

 

 Notes:  You may need to either implement the cacheObject method or delete the cacheObject method from the AxFeatureRequest class. Also you will need to delete the cacheRecordRecord or implement that method as well from the AxFeatureRequest class.

Create an Inbound Port for Your Service Operations

After the wizard is complete we must expose our service via an Inbound Port. This can be done within the Microsoft Dynamics AX client in the System Administration -> Services and Application Integration Framework -> Inbound ports area.  Create a new port with the following settings 

Property

PropertyValue

 

 

Port Name

 

 

 

 

FeatureRequestPort

 

 

Service Operations

 

 

 

 

FeatureRequestService.create

 

 

 

FeatureRequestService.delete

 

 

 

FeatureRequestService.find

 

 

 

FeatureRequestService.findKeys

 

 

 

FeatureRequestService.getChangedKeys

(this requires Microsoft SQL Server change tracking to be enabled)

 

 

FeatureRequestService.getKeys

 

 

 

FeatureRequestService.read

 

 

 

FeatureRequestService.update

 

 

 

Customizing Microsoft Dynamics CRM to Support Bi-Direction Data Integration 

Create Custom Components

Now that the Microsoft Dynamics AX side of things is customized we need to focus on the Microsoft Dynamics CRM customizations that are needed. We will need to create the following components in Microsoft Dynamics CRM

Component

Name

Property

Property Value

Solution

Feature Request Solution

 

 

 

 

Display name

Feature Request Solution

 

 

Name

FeatureRequestSolution

 

 

Publisher

Any Publisher Value Will Work. I created a new publisher with prefix of frsp

 

 

Version

1.0.0.0

 

 

 

 

Entity

Feature Request

 

 

 

 

Display Name

Feature Request

 

 

Plural Name

Feature Requests

 

 

Name

frsp_featurerequest

 

 

Ownership

User or Team

 

 

Notes

Yes

 

 

Activities

Yes

 

 

Connections

Yes

 

 

Duplicate Detection

Yes

 

 

Primary Field Display Name

Name

 

 

Primary Field Name

frsp_name

 

 

Maximum Length

50

 

 

 

 

Field (Feature Request)

Requested Date

 

 

 

 

Display Name

Requested Date

 

 

Name

frsp_requesteddate

 

 

Type

Date and Time

 

 

Format

Date Only

 

 

 

 

 

Feature Id

 

 

 

 

Display Name

Feature ID

 

 

Name

frsp_featureid

 

 

Type

String

 

 

Maximum Length

20

 

 

Requirement Level

Business Required

 

 

 

 

 

Feature Description

 

 

 

 

Display Name

Feature Description

 

 

Name

frsp_featuredescription

 

 

Type

Multiple Lines of Text

 

 

Maximum Length

1000

 

Configuring the Microsoft Dynamics CRM 2011 Adapter

In order to map the custom entity in the Connector for Microsoft Dynamics client we must configure the Microsoft Dynamics CRM 2011 Adapter. This is requires executing that adapter’s configuration utility.

  1. Launch the Connector for Microsoft Dynamics Client
  2. Click the settings node in the tree view for the already existing Microsoft Dynamics AX 2012 to Microsoft Dynamics CRM 2011 integration
  3. Click the link on the right under the Microsoft Dynamics CRM 2011 Settings for the Configure Microsoft Dynamics CRM utility
  4. Once the configuration utility has started click “Next”
  5. Enter the credentials for a Microsoft Dynamics CRM Administrator account
  6. Click Get Organizations
  7. Select the Organization where your custom entity exists
  8. Click Next
  9. Scroll down the tree view of check boxes until you find the “Feature Request” entity. Check the box
  10. Check the box for “Skip complete configuration and only generate entity configurations”
  11. Click Next
  12. Click Configure
  13. Click Finish
  14. The utility will close

Configuring the Microsoft Dynamics AX 2012 Adapter

In order map the custom AIF document service in the Connector for Microsoft Dynamics client we must configure the Microsoft Dynamics AX 2012 Adapter. This requires executing the adapter configuration utility.

  1. Launch the Connector for Microsoft Dynamics Client
  2. Click the settings node in the tree view for the already existing Microsoft Dynamics AX 2012 to Microsoft Dynamics CRM 2011 integration
  3. Click the link on the right under the Microsoft Dynamics AX 2012 Settings for the Configure Microsoft Dynamics AX utility.  (You must run this utility as a Windows user that is in the admin group within Microsoft Dynamics AX 2012)
  4. Once the configuration utility has started click Refresh services
  5. Check the check box in the tree view for the FeatureRequestDocumentService
  6. Click Configure
  7. Click the OK button on the message box that is shown
  8. Close the Microsoft Dynamics AX 2012 Configuration utility

Important Note:

Due to a limitation that is currently being worked on you must change the QueryName attribute in the object provider configuration file that is generated for your Document Service. You must change the QueryName attribute from the Query your Document Service is based upon to the class name which represents your document. Usually this will be something like Axd<Class Name>. In this case it will be AxdFeatureRequestDocument.

This file can be located in %ProgramFiles(x86)%\Microsoft Dynamics\Microsoft Dynamics Adapter\Adapters\Microsoft.Dynamics.Integration.Adapters.Ax2012\ObjectConfig\<AOSServerName_DocumentPort>\

In this example the file should be called FeatureRequestPort_FeatureRequestDocumentService.config

The XML that needs to be adjusted would look like this before and after the change:

Before:

<RootDefinition Name="AxdEntity_FeatureRequest_1" TypeName="AxdEntity_FeatureRequest_1" DisplayName="Feature Request Document Service" IsRequired="false" IsReadOnly="false" QueryName="FeatureRequestQuery" ID="478ef2fe-b623-4f2f-8460-845df5720444" ServiceName="FeatureRequestDocumentService" PortName="FeatureRequestPort" SupportedOperations="Create, Delete, FindKeys, GetChangedKeys, Read, Update" RootDataSourceName="FeatureRequest_1" KeyInfo="RecId">

After:

<RootDefinition Name="AxdEntity_FeatureRequest_1" TypeName="AxdEntity_FeatureRequest_1" DisplayName="Feature Request Document Service" IsRequired="false" IsReadOnly="false" QueryName="AxdFeatureRequestDocument" ID="478ef2fe-b623-4f2f-8460-845df5720444" ServiceName="FeatureRequestDocumentService" PortName="FeatureRequestPort" SupportedOperations="Create, Delete, FindKeys, GetChangedKeys, Read, Update" RootDataSourceName="FeatureRequest_1" KeyInfo="RecId">

 

Creating Bi-Directional Maps for Your Microsoft Dynamics AX Document Service and Microsoft Dynamics CRM Custom Entity

In order to get data to flow you must create new maps for your custom document service and custom entity.

Microsoft Dynamics AX 2012 Document Service to Microsoft Dynamics CRM 2011 Custom Entity Map

The first step is to create a map that flows data from Microsoft Dynamics AX to Microsoft Dynamics CRM.

  1. Open the Connector for Microsoft Dynamics Client
  2. Expand the Integration and Site for your existing Microsoft Dynamics CRM and Microsoft Dynamics AX integration
  3. Click Maps nodes
  4. Click New Map on the tool bar
  5. A dialog window will be shown
  6. On the Source Entity list select Feature Request Document Service under Microsoft Dynamics AX 2012 \ <Company Name>
  7. On the Destination Entity list select Feature Request under the Microsoft Dynamics CRM 2011 \ <Organization Name>
  8. Click Create
  9. Perform the following mappings

Destination

Mapping

Feature ID

Feature Id

Name

Feature Name

Feature Description

Feature Description

Feature Request

CreateGuid(DAX Integration ID) *

Integration Key

Feature Id

Requested Date

Requested Date

* CreateGuid is a function in the mapping it will show as =CreateGuid(DAX Integration ID) 

10.   Change the map settings as followings

Setting

Value

Check for Changes

Every 30 Seconds

Check for Data Modified After

12/31/1899

 

 

11.   Save the map

Microsoft Dynamics CRM 2011 Custom Entity to Microsoft Dynamics AX 2012 Document Service Map

 

Now we must create the map in the other direction.

  1. Open the Connector Client
  2. Expand the Integration and Site for your existing Microsoft Dynamics CRM and Microsoft Dynamics AX integration
  3. Click Maps nodes
  4. Click New Map on the tool bar
  5. A dialog window will be shown
  6. On the Destination Entity list select Feature Request Document Service under Microsoft Dynamics AX 2012 \ <Company Name>
  7. On the Source Entity list select Feature Request under the Microsoft Dynamics CRM 2011 \ <Organization Name>
  8. Click Create
  9. Perform the following mappings

 

Destination

Mapping

DAX Integration Id

Concatenate(“{“, Feature Request, “}”) *

Feature Description

Feature Description

Feature Id

Feature ID

Feature Name

Name

Requested Date

Requested Date

 

* Concatenate is a function in the mapping it will show as =Concatenate(“{“, Feature Request, “}”)

10.   Change the map settings as followings

Setting

Value

Check for Changes

Every 30 Seconds

Check for Data Modified After

12/31/1899

 

 

11.   Save the map

Testing the Integration

Now that the maps are created we can activate them. 

  1. Open the Connector for Microsoft Dynamics Client
  2. Expand the Integration and Site for your existing Microsoft Dynamics CRM and Microsoft Dynamics AX integration
  3. Click Maps nodes
  4. Locate the maps we created and for each map right click the map and click Activate Map
  5. Then click the Save button on the tool bar

The final test is to enter some data. For Microsoft Dynamics AX we did not create a form to enter data, but we can do so quickly to make an easy way to enter a record. You can follow the MSDN article on “How to: Create a Simple List Form [AX 2012]” here: http://msdn.microsoft.com/EN-US/library/hh538488.aspx

For Microsoft Dynamics CRM we can customize the Microsoft Dynamics CRM form to add the fields we want to add.  The data should now be able to flow in both directions.

I would like to personally thank our support engineers for developing this post as well as for assisting all of our customers!  Stay tuned for an in-depth video series on this topic as well.

Comments (38)
  1. Good post.. Thank you very much..

    Pls give me some example for parent and child table mapping in connector from ax 2012 to crm 2011 by using single query.

  2. Hi,

    I have followed the exact steps as mentioned above.

    After inserting data into AX entity, same reflecting in CRM entity. But vice versa does not working in my case.

    Could yoy please help me on this?

    Thanks & Regards,

    Yogesh Mulay

  3. thehetz says:

    @Abbas – you could take a look at how the ConnCustomerOrg query is built and how that service is mapped in the default Connector maps.  This will provide you with an excellent example of how to build the query in Microsoft Dynamics AX 2012 as well as how to map the resulting service into Microsoft Dynamics CRM 2011.

  4. thehetz says:

    @Yogesh – Please ensure that the mapping from Dynamics CRM to Dynamics AX is correct.  Also, are records in CRM being found but failing to integrate or are they simply not found in CRM?

    Past that you might want send me an email directly to work through what you are seeing.

  5. @thehetz: After integration, when I insert/update the record in AX entity it automatically gets inserted into CRM entity. But when I insert the record into CRM entity or update the record in CRM entity, it does not comes to AX entity.

    AX to CRM record insert/update working fine. But CRM to AX record insert not working in my case.

    Please help.

  6. thehetz says:

    @Yogesh – Please ensure that the mapping from Dynamics CRM to Dynamics AX is correct.  Also, are records in CRM being found but failing to integrate or are they simply not found in CRM?  You can determine this by watching the Connector client while the map is running, if the status indicates that n number of records were found, then it is finding records in CRM.  You can also turn on tracing to get a deeper view into what is happening.

  7. @thehetz – Hi, I have installed connector on AX server and configured adapters for CRM 2011 and AX 2012 on AX server. I am not gettnig any error. I am just not getting data into AX form from CRM entity. But I am getting data into CRM entity from AX form. Need help on this. Is it becasue of DaxIntegrationId field mapping?

    Please help on this.

  8. thehetz says:

    @Yogesh – I am going to need more Context to be able to help you with this.  Have you opened a support ticket?  Please use the contact blog author feature to contact me directly.  Thanks

  9. Ahmed Maqsood says:

    Hi, I have the same requirements apart from that the Custom Table in AX will be synchronised from Custom Table in CRM. It is working to extend that when a new record is created in CRM it is replicated in AX and if we change it in AX it updates the existing record in CRM, (Great!), but if we update the exiting record in CRM it tries to create a new record where as it should update the existing record which was created earlier as a result of synchronisation. Cannot get it to work have tried different things, where i am doing wrong? Please HELP!

  10. thehetz says:

    @Ahmed – it sounds like the integration is not finding the record in Dynamics AX when it finds that a record has changed in Dynamics CRM.  Have you implemented the DAXintegration ID column on your table in Dynamics AX as a GUID and do you have it mapped properly on the map?  Did you add the code in AX to update the GUID properly?

  11. Maqsood Ahmed says:

    Thank you very much @thehetz!

    The field in the AX table "DAXIntegrationId" was "DAXIntegrationID" instead 🙁

    I over looked the notes.

    Regards

    Maqsood

  12. shan says:

    HI,

    Currently I'm Using Ax2012 R2 Cu7, Im unable to get the dynamics connector Class, i just have connectorhelper, As per your example for in the Insert method, used a eventhandler with the help of dynamics connector- SetDAXIntegrationId. Kindly help me what should i do now.

  13. Van Sun says:

    Hi,

    Im getting this xxxx has encountered an error. Processing will be aborted. Error text: The endpoint associated with contract "XXX" is not found. Could you kindly throw some light on this issue?

  14. thehetz says:

    @Van – you most likely need to re-compile AX and do a full CIL build as well.  Then restart the Connector service.

  15. thehetz says:

    @Shan – the Connector Helper class is the one that you want to work with, that was an update in CU 6.

  16. Van Sun says:

    @ Thanks thehetz, for the information provided, now I get this error " XXXX has encountered an error. Processing will be aborted. Error text: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state." Could you kindly help me in this

  17. thehetz says:

    @Van – I suggest restarting the AOS and Connector services.  If this doesn't fix the issue then I would compile AX and do a full CIL build.

  18. Van Sun says:

    Thanks a lot theHetz, Got 1 working getting error in another one. "Object Reference not set to an instance of an object", after Creating the map and try to run the map. Plz advice

  19. thehetz says:

    @Van – please ensure that you are setting the proper value for the QueryName attribute in the service object definition configuration file.  It needs to be set to the AxdClass name rather than the QueryName.

  20. Jithu says:

    Hi thehetz,

    While mapping the field street – Im getting the below error – "Unable to assign field of type, string to field of type Dictionary{2}".Kindly help

  21. thehetz says:

    @Jithu – you will need to use a function to get at this value properly.  Take a look at how the street field is mapped on the Customer to account map.

  22. George says:

    Hello,

    The map from CRM to AX does not work, I have the error: "Type FeatureRequestQuery not found in ProxyAssembly."

    but the query is present in AX and I have compiled after creating the query and everything else.

    Any suggestion?

  23. George says:

    I have solved the issue "Type FeatureRequestQuery not found in ProxyAssembly.", I think it was that after modifying the xml file I regenerated it so I lost the modification.

    @thehetz: could yo uplease update this document for AX2012 R3? The SetDAXIntegrationId is not present in the class ConnectorHelper that replaces DynamicsConnector.

  24. Mobeen says:

    I have tried your sample it work perfect when I create a record from AX to CRM. But when I try to create record from CRM to AX I get this error

    "'F3SalesQuotationTableServiceClient' does not contain a definition for 'create'".

    Our service contain create function and also deployed on Inbound port. The configuration file also shows it has this function. Below is the XML

    <RootDefinition Name="F3SalesQuotationTableService" TypeName="AxdEntity_SalesQuotationTable" DisplayName="F3 Sales Quotation Table Service" IsRequired="false" IsReadOnly="false" QueryName="AxdSalesQuotationTable" ID="cfe929d5-6aae-475f-8608-9aaeb0f4d655" ServiceName="F3SalesQuotationTableService" PortName="F3SalesQuotationTableServices" SupportedOperations="Create, FindKeys, GetChangedKeys, Read, Update" RootDataSourceName="SalesQuotationTable" KeyInfo="QuotationId">

       <ServiceOperations xmlns="">

         <Operation OperationType="Create" Name="create" MethodName="create" />

         <Operation OperationType="Find" Name="find" MethodName="find" />

         <Operation OperationType="FindKeys" Name="findKeys" MethodName="findKeys" />

         <Operation OperationType="GetChangedKeys" Name="getChangedKeys" MethodName="getChangedKeys" />

         <Operation OperationType="GetKeys" Name="getKeys" MethodName="getKeys" />

         <Operation OperationType="Read" Name="read" MethodName="read" />

         <Operation OperationType="Update" Name="update" MethodName="update" />

       </ServiceOperations>

     </RootDefinition>

    Please help me out what should I do ?

  25. thehetz says:

    @Mobeen – I would suggest recompiling the AX AOT and then doing a full CIL build as well.

  26. Anonymous says:

    Thanks for the reply thehetz.

    I have ran into another problem in custom entity. I was able to map all the entities in connector. There is a customer foreign key in my custom entity when I try to sync it from AX to CRM it does not get synced.

    I have used the same mapping as sales order but still no success. On digging into the issue I saw that integration key for customer is combination of accountnumber and guid on CRM side. AX only sends account id. This happens in Sales entity also, in sales order it maps properly but my entity doesn't any idea what I am doing wrong ?

  27. thehetz says:

    @anonymous – you will need to map in the DAXIntegrationId for the customer, which will need to be made available in your service within AX.

  28. Ahmad Abu Eid says:

    Hi thehetz,

    Great tutorial, thanks.

    I got the error below, any idea ?

    The endpoint associated with contract ":AbTestService" is not found.

  29. Ahmad Abu Eid says:

    I am using ax 2012 r2 and CRM 2015 online

  30. thehetz says:

    @Ahmad – the only thing that I can think of would be some sort of issue with the publishing of the custom AX service.  Perhaps doing a full re-compile and a full CIL build would correct it?

  31. kirit kapupara says:

    Hi I was trying to AX to CRM integration but only AX to CRM customer creation is working but when i update the customer from AX then it will not reflect in CRM. and also when i create customer from CRM then it will not created in AX. means AX to CRM only create operation is working update operation is not working and CRM to AX totally not working.please help me.thanks

  32. thehetz says:

    @kirit – I suggest that you open a support case for this issue as it seems too complex to handle in this forum.

  33. Swapnil says:

    @Ahmed Maqsood,
    Hi
    I have same issue that CRM record is inserted in AX but not updated same record from CRM to AX.
    have u find any solutions.

    Thanks

    1. Sathish says:

      Hi
      I have same issue that CRM record is inserted in AX but not updated same record from CRM to AX.
      have u find any solutions.

  34. siuchon says:

    Hi thehetz,
    I created a custom document service in AX 2012 with name “Conn Open Stm Service”. Then, I’ve deleted that service. I created a new one name “Conn Open Statement Service”. But when I created the new map in the connector, the old one still there. How can I refresh the connector, so that the old one disappear from the connector? Thanks.

    1. thehetz says:

      Most likely you still have an object provider configuration file for the old service in the AX 2012 adapter \ ObjectConfig folder. Take a peek in that folder and if there is one, delete it. Restart the client.

      1. siuchon says:

        Hi thehetz,
        it worked. Thank you very much.

        1. thehetz says:

          Thanks for letting us know! And glad to hear that you were able to move past the issue.

Comments are closed.

Skip to main content