My state of mind at this moment is hard to describe, but Malin Martnes sendt me this link from Urban dictionary 😂
This is Part 2 of the Gateway SETUP
The final settings
This is where we left off in the last post:
We need to do one config in CRM/CDS before we continue. For the integration to work we need to create a KEY for it to match on. The source doesn’t know of GUID, so I create a key for “Account Number”. In Norway we are lucky that this number is unique and applies to all organization’s.
Open the entity you are integration to (Account for me), and create a new field called KEY. I am choosing to use the “Account Number” field here as my Unique KEY. Remember to publish changes!!
First thing I do is limit the number of accounts while testing.
Then I remove all the blank fields in the KEY, to make it equal to the user input in Dynamics. You don’t have to do this, but chose to for simplicity.
In the next step you choose the entity to connect to in CDS/CRM, and map the field. I am choosing to only map “Name” and “Account Number” during the test.
And the magic continues. Here you can setup how often you wan this awesome sync to happen. Our data is fairly static, so once a week is fine:)
Wait until the query is done, and check out the newly created/updated Accounts in Dynamics. This is just a gamechanger for me.
Pricing (a little uncertain)
As far as I can see/understand, this is using Azure Message bus, and it prices everything to messages pr hour. Below is a snipp from https://azure.microsoft.com/en-us/pricing/details/service-bus/ In my case this would practically be “free”.
|Operations||$0.05 per million operations|
|Base charge 1||$0.0135/hour|
|First 13M ops/month||Included|
|Next 87M ops (13M–100M ops)/month||$0.80 per million operations|
|Next 2,400M ops (100M–2,500M ops)/month||$0.50 per million operations|
|Over 2,500M ops/month||$0.20 per million operations|