A few days ago Microsoft have the Flow connector available for preview, and you can read more about it here. What I wanted was to see if I could make a very simplified flow, where a customer is created in CRM, and then transferred to Dynamics AX.
The flow therefore consists of the following steps, when a record is created in CRM, a customer is created in AX. After that, I wanted an email to be sent to me.
To test this flow, I created a Customer in CRM online.
Then I waited for a few second, and then the customer was visible in AX. I just became very impressed.
I also received an email, telling me that a new customer was created in AX from CRM, and that made be even more happy.
If I when in and analyzed what happened, I could trace the entire integration in Flow, and also see how much time spent on processing each step. In this case, I see that AX used 10 seconds to process the JSON/ODATA message, and spent 3 seconds to sending me an email that the record was created.
Here are the steps I used to create this flow. First I select the Flow action “Dynamics CRM Online – When a record is created”.
Then I specify the organization and the entity name: Accounts
Next I add the action Dynamics AX Online – Create a record
And I select the instance, and what user I should log in with. I also select the entity name: Customers, and select to only transfer the Account number and Account name into the AX entity. Some of the other fields, I choose to hardcode for simplicity reasons.
The last step is to send an email to myself
Some summary.
Using Dynamics AX with flow will certainly be the way forward on how we integrate AX with CRM and all kinds of other 3’rd party systems. It is still in preview, and the next thing we are waiting for is that Dynamics AX can get reactive, and then when a record is created or modified inside AX, this can trigger a flow. But Microsoft have promised that this is on its way. Also remember that this tool has its current restrictions and that we need to be patient and let Microsoft further develop and improve its capabilities. But for easy and simple integrations I would call this as a unique opportunity to get rid of complex and time consuming integrations. As long as you keep it simple it works as intended.
Thanks Microsoft, keep it coming!
The flow therefore consists of the following steps, when a record is created in CRM, a customer is created in AX. After that, I wanted an email to be sent to me.
To test this flow, I created a Customer in CRM online.
Then I waited for a few second, and then the customer was visible in AX. I just became very impressed.
I also received an email, telling me that a new customer was created in AX from CRM, and that made be even more happy.
If I when in and analyzed what happened, I could trace the entire integration in Flow, and also see how much time spent on processing each step. In this case, I see that AX used 10 seconds to process the JSON/ODATA message, and spent 3 seconds to sending me an email that the record was created.
Here are the steps I used to create this flow. First I select the Flow action “Dynamics CRM Online – When a record is created”.
Then I specify the organization and the entity name: Accounts
Next I add the action Dynamics AX Online – Create a record
And I select the instance, and what user I should log in with. I also select the entity name: Customers, and select to only transfer the Account number and Account name into the AX entity. Some of the other fields, I choose to hardcode for simplicity reasons.
The last step is to send an email to myself
Some summary.
Using Dynamics AX with flow will certainly be the way forward on how we integrate AX with CRM and all kinds of other 3’rd party systems. It is still in preview, and the next thing we are waiting for is that Dynamics AX can get reactive, and then when a record is created or modified inside AX, this can trigger a flow. But Microsoft have promised that this is on its way. Also remember that this tool has its current restrictions and that we need to be patient and let Microsoft further develop and improve its capabilities. But for easy and simple integrations I would call this as a unique opportunity to get rid of complex and time consuming integrations. As long as you keep it simple it works as intended.
Thanks Microsoft, keep it coming!
