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).
You are here
While it’s always important to keep tabs on what operating system versions are supported for which CRM versions, the recent release of CRM 2016 means that Microsoft has moved on while many organizations may be in the process of evaluating the upgrade before taking the dive. With OS upgrades being pushed out to tablet and phone users on an increasingly regular basis, it has become even more vital to know which updates your users should wait to apply.
Today’s fast-paced, mobile customers have come to expect quick responses and personalized attention in their interactions with customer service groups in the companies they do business with. The consequences of a poor customer experience can be swift and direct. A recent study by PH Media Group found that over half of respondents would switch loyalty due to one negative service experience with a company.
MS CRM has a limitation that when you create an email template to use in a workflow, you can only base the template on a predefined list of entities. Adding to that is the frustrating fact that once you choose the source entity you can only add fields from a predefined list of related entities, so accessing fields from a custom entity isn’t possible with out of the box functionality.
With CRM 2016, came the Web API; a new endpoint allowing the creation, deletion, update and retrieval of CRM data. While Microsoft has stated that the old 2011 endpoint will remain in order to support backwards compatibility, it has been deprecated, and ideally should not be used for new development.
When it comes to displaying images on your web portal powered by ADX studio, ADX recommends the use of attachment notes as a storage for images. This approach comes with a lot of benefits since it allows the storage of images with various sizes and aspect ratios. The disadvantage of this approach is that it’s rather cumbersome in CRM directly. It provides a rather detached experience when assigning images to entities that in one way or the other will be used as visual assets on the portal.
While it is commonly suggested that IExecutionContext.Depth should be used to prevent infinite loops in your plugins, IExecutionContext.SharedVariables can give you finer control over what your plugins are doing, in certain cases. Even better, Shared Variables provide a way to pass values from one plugin to another, as long as they’re in the same sequence of steps for a particular message.
The new kid on the block has arrived. Microsoft announced, yesterday, the release of the newest version of its Customer Relationship Management (CRM) product, called Microsoft Dynamics CRM 2016. This release is said to be Microsoft’s most comprehensive offering yet, supporting a new era of customer engagement.