To successfully integrate our products with custom entity-forms, the navigation configuration has to be applied manually.

This article describes, how MS Dynamics CRM Menu Navigation Links can be added manually to DocumentsCorePack and ActivityTools.

This article describes how to define custom parameters for embedded ActivityTools pages (For example to pre-filter activity types).

This article is about the DocumentsCorePack (DCP) FileExplorer in IFD environments for CRM 2011, 2013, 2015 and 2016.

Basically, DocumentsCorePack's FileExplorer is not supported in CRM IFD environments. Nevertheless, it could be possibly working. If you want to try to configure it, follow this article.

This articles explains how you can add custom columns to ActivityTools grids for CRM 2015/2016.

Via a CRM settings key additional columns can be added to the ActivityTools grid. For each activity type and column, a separate CRM field can be displayed. The custom columns will be inserted between the subject- and date/time-column and can have column headers. This is a global setting and takes effect for all CRM users.

Sharepoint Documents Button Error – SmartBar 

 If you encounter an error, after -clicking- on the Documents Button inside SmartBar 2015/16 please follow this blog article. 

SmartBar is per standard using the Client-based SharePoint integration view. If you instead use the Server-based integration on your CRM System, your click could result in one of the following errors:

When you try to delete a solution, it will show you an error message if there are any dependencies.

To solve this issue, please follow the steps below.

Because the call for a Field Search in our DocumentsCorePack Client grew louder and louder, we decided to implement one.

Please note: The Field Search is available in version 7.101 and later versions.

In order to apply special settings to your DocumentsCorePack Template, you have to access the Template Settings Dialog.
How to get to this essential dialog is outlined step by step in this article.

Certain properties of DocumentsCorePack templates consist of fixed text
and Dynamics 365 fields. There are also some additional function calls available and data
from Dynamics 365 can also be manipulated.

Template settings are additional capabilities that can be defined in your DocumentsCorePack templates.
The purpose of most of the settings is to improve the automation of the document generation process.