If we can offload some of that logic processing elsewhere then we can improve the overall performance of the CRM system.
So why would you want to send this to a service endpoint like the Azure Service Bus? Often the CRM asynchronous service is over taxed it is responsible for so much in the CRM system now. I have posted a sample contact create data context in JSON here so you can get an idea of all the data it contains as well as its format. It is the same data context that you work with when building a plugin so it also will contain your input parameters, pre and post images, the execution depth, the entity logical name, and what CRM message is being executed (create, update, delete, etc.). Things like a newly created contact ID, the created by system user ID, any option sets that had a default value, and a lot more. So if you were to create a contact with first name and last name, the data context would contain that data as well as any other default data as part of the create itself.
The data context contains all of the business data that is processed as part of the CRM message. An often forgotten feature is its ability to notify a service endpoint with the data context of the particular CRM message that it is registered on. Once I switched to the new Discovery URL, I was able to log in without a problem and do my Plugin Registration.CRM developers and even end users know of the asynchronous service in CRM the service is usually associated with workflow processes or plugins.
On that page, you will see the Discovery URL (among other useful URLs) that you will need. If you have a doubt as to what the exact Discovery URL you should be using for your Plugin Registration, log into the CRM Online instance directly, go to Settings > Customizations > Developer Resources. In the new way of connection, you have to change that Discovery URL to: In the older way of connecting, that I was used to, I would create a new connection with the Discovery URL set to: I spent over 30 minutes trying to find the solution to this issue, which eventually led me to a Microsoft community forum in the UK that explained the Discovery URL had changed. Then, when I tried to connect to the new instance, I was getting an Authentication Failure before it even listed the organization names. Up until now, I had been connecting to the old CRM Online instances, which always worked fine. Apparently, Microsoft changed the way the Plugin Registration is done when they integrated the CRM with Office 365.
0 kommentar(er)
