When you launch an upgrade installation of our products, the setup will update existing files and solutions in CRM. The default behaviour of upgrading a product installation has changed with all releases after 1st of March, 2013.
Thanks to this feature of ActivityTools, you can easily embed the ActivityTools previews to your CRM dashboard.
Depending on your configuration, it is possible to show one or mutliple previews in one dashboard.
As a preparation of the now rescheduled cross browser compatiblity for RU8, older versions of ActivityTools already had preparations built in, which will cause the Activity & Queue preview to fail. Please update to the latest Version to fix this issue.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to email@example.com.
ActivityTools default user settings can be predefined as follows:
Define the default settings for EmailPreview
Create a new settingskey called DefaultViewEmail as described here.
On some occasions, unmanaged customizations to forms might prevent the setup to correctly configure the navbar section of entities.
You would see an error similar to this one, telling about a transition of an unmanaged solution being impossible.
Figure 1: Error message (unmanaged solution)
This blog article will walk you through the required steps on how to install GroupCalendar and ActivityTools in a claims-based environment.
This article is valid for GroupCalendar for CRM 2011, 2013, 2015 and 2016 but only for CRM 2013 and older versions of ActivityTools. From CRM 2015 onwards ActivityTools does not have to be configured for IFD anymore!
The steps are the same for both products, so instead of an explicit product name, we will use the term the addon in this guide.
++++++++++++++++++++++++++++++++++++++++++++++++++ Please note:This article applies to ActivityTools inMicrosoft Dynamics CRM 2011 and CRM 2013
(Click here for information on how to enable debugging in ActivityTools in higher CRM versions)
To successfully integrate our products with custom entities, these custom entites either have to be part of a managed solution or the navigation configuration has to be applied manually.