You are here
Recently, in Dynamics CRM, we were coming across some issues with the processing of async services (specifically plugins). The environment was pretty robust, but we had a lot of processes going on, and we would frequently see the async services max out what memory we had available on the server, which required a restart of the services (not ideal).
As part of a sample store locator application, I needed to geocode the addresses in order to mark them on a map (see Figure 5). The Google Maps Geocoding API makes the process pretty easy, so I thought I would just leverage a LINQPad query to call the API.
I have a list box in QlikView that has an order status field. It had three values: Open, Posted and Deleted. I had a situation in QlikView where when the document opens I wanted to select Open and Posted, but not Deleted. Someone suggested that I use Open|Posted in the search string. Unfortunately, that didn’t work. I searched and searched and found plenty of different ways suggesting to do it and none worked except for using a macro. I didn’t want to use a macro and I knew there had to be a way.
Sometimes in CRM we have times when we need to complete an action without allowing the user to change any fields. There are many ways to go about doing this, but one of the easiest is to display a modal over the form. It prevents the user from clicking on and changing any fields, while also providing a helpful message to the user, letting them know that there is an action in progress.
Dynamics CRM offers integration with Windows Azure, so I decided to setup a basic example of having updates to the account entity in CRM sent to an Azure Service Bus queue. I am using CRM online, which comes pre-configured to work with Azure. If you’re using CRM on-premise, see the Configure Azure integration with Microsoft Dynamics CRM.