CRMGamified is a Microsoft Certified Partner in CRM and their mission is to provide you with solutions to get the most out of your CRM!

With Hurrah!® and Motivation Engine together they build highly engaged teams, who produce better results, sell more, service better and work harder.

Hurrah!® will help you measure key performance indicators in real time through exciting TV-Like dynamic leaderboards and motivate your sales force, inspiring the revenue-generating behaviors.
It’s easy to install and manage and it is a highly customizable tool that can be adapted to any industry and Dynamics CRM implementation.

CRMGamified® Motivation Engine is an easy to install add-on designed especially for Microsoft Dynamics CRM, aimed at inspiring the key behaviors that drive more sales, generating actual business results, better CRM data quality and CRM user engagement.

Backed by a talented team CRMGamified® is the result of a hardworking, full-time agile development team who’s continually adding features based on customer feedback.

To learn more about CRMGamified® visit them at crmgamified.com

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

We are back from our business journey of this year’s Convergence 2015 (March 16-19) in Atlanta GA.

THANK YOU for visiting our booth!

Figure 1: Microsoft Convergence 2015

Highly motivated, strengthened with coffee and always with a smile on the face we set up our booth early in the morning.

Figure 2: Setup of the booth

This year, we brought our brandnew logo-wall to the Convergence – an appropriate background to welcome our guests!

Figure 3: mscrm-addons.com logo-wall

We are back: once our booth was set up we changed our outfit from casual to business – and were more than ready to start:

Figure 4: Our team - ready to start! 

In the middle of the happening:

Figure 5: Our booth was well visited...

Convergence is a great platform for us and other business leaders to showcase our Add-Ons to the audience.

Figure 6: ... by many interested and interesting people

Business before pleasure: After a long day full of interresting peoples and conversations we enjoyed the fanstastic framework program. 

Figure 7: Framework program

Of course, we did not miss the chance to shoot pictures of One Republic for our co-workers in Austria (sorry ladies, but we were too far away to catch the T-shirt ;) ). 

Figure 8: One republic

We even had time to walk through Centennial Olympic Park. 

Figure 9: Centennial Olympic Park, Atlanta

For those who couldn’t make it to the Convergence, the next chance is eXtremeCRM 2015 (April 21-23) in Madrid, Spain! See you there at booth #T-106!

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This blog article outlines how to create SharePoint locations, folders and subfolders automatically within MS Dynamics CRM with DocumentsCorePack ServerBased, using a simple workflow.

Add-On: DocumentsCorePack ServerBased (OnPremise)

For the MS Dyn CRM Online version of this article, please click here.   

Example:

Standard SharePoint location in CRM:

 

Figure 1: Standard CRM SharePoint window

Created SharePoint location:

Figure 2: Created SharePoint location

Generally, when creating a new account in MS CRM, all appropriate documents (e.g. quotes, invoices etc.) are saved in the entity Documents in MS CRM.
As you can see in Figure 3, the CRM Save location Documents can be accessed via the drop-down-button next to the current company in the main navigation area at the top. 
It could as well be accessed using our addon SmartBar, which enables a simple navigation between all related CRM records and entities.

 

 
Figure 3: Save location of documents in MS Dynamics CRM 

Anyway, to create a new Account in CRM, navigate to Accounts, then click on the [New]-button. 

Figure 4: Create a new account in MS CRM.

When you click on Documents (see Figure 3), the following message box appears. The box indicates, that a SharePoint location will be created manually with a click on the [OK]-button.

Figure 5: Message from webpage

The standard SharePoint location-window is empty and does not contain any folder(s) or subfolder(s).

 
Figure 6: Entity Documents, once an account has been created. 

Once documents have been saved, its look changes. 

Figure 7: Entity Documents with saved content
 

How to create a workflow that automatically generates SharePoint locations, folder(s) and subfolder(s) when creating an account

It is possible to create different subfolders in folders that contain certain documents (e.g. Quotes, Invoices …)

This can be managed with a simple workflow. 

In our example we define 

1) the SharePoint location,
2) the folder(s) and 
3) the subfolder(s) 
that will be automatically triggered when creating a new account. 

First of all, open your CRM and navigate to Settings and Processes.

Figure 8: CRM > Settings > Processes

Now create a new process with a click on the [New]-button.

Figure 9: Create a new process

In the next window, define the following settings:

- Process Name: (here: CreateFolder)  
- Activate As: Process 
- Entity: (here: Account)     
- Category: Worfklow

Once this is done, click on the [Add Step]-button, select AutoMergeWF and CreateSharePointFolder. 

Figure 10: Add a new step (CreateSharePointFolder)

Now name the step (here: CreateFolder) and click on the [SetProperties]-button:

Figure 11: Name the new step 

In the following window, define the SharePoint location, folder(s) and subfolder(s).
For example: TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 12: Example SharePoint subfolder added

Figure 13: Structure of TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 13 outlines, that a slash indicates that the subfolder remains in a mainfolder. Furthermore, it outlines that a semicolon indicates the creation of a new main folder. 
Please note: the folder and/or subfolder name can contain blank space but you must not use a blank space between a folder and its subfoler(s) 

Once you have set up your order structure, please click on the [Save and Close]-button (see Figure 12). 

Now click on the [Activate]-button in order to activate your workflow:

Figure 14: Activate workflow

Then click once again on the [Activate]-button in order to confirm the process:

Figure 15: Confirm the process

Now your workflow is activated.

Figure 16: Activated workflow

Please note: it can take some minutes until the workflow has been entirely finished!

When you now create a new account and then navigate to the SharePoint document location, it should look similar to the example in Figure 17<. 

Figure 17: Example - SharePoint document location based on workflow

When opening the TEST-folder, the subfolders look as shown in Figure 18 and Figure 19.

Figure 18: Subfolder I

Figure 19: Subfolder II

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This article explains how to create label templates with DocumentsCorePack (DCP) DocX.

Requirements: DocumentsCorePack for MS CRM 2013 (Client 6.33) and higher

Generally, there are two options to create and merge a label template.

Option A) Select various records at once - each label equals one record from the main entity of the template.
(e.g. if you want to merge an account label template for a few companies, you can select different companies at once. As a result, you get one label per selected account) 

Example

Figure 1: Merged account lable template - example

Option B) Select one record and set relations - each label equals one record from the predefined relationship. 
(e.g. if you want to merge an account label template for one company (but different employees) you can select one company to receive all related contacts. As a result, you get one label per related contact).

Please note: With option B, it is mantadory to set a regarding relationship when creating the template in advance. 

Example: 

Figure 2: Merged account lable template - example

Option A) 

Please note: In General, all Microsoft Word formatting options are supported. However, the label template must be created in advance and saved as .docx!

1) Open MS Word and navigate to the www.mscrm-addons.com-tab and click on the [Insert MailMerge Fields]-button.

Figure 3: Open the DocumentsCorePack Task Pane.

2) In the following question box, click on the [Yes]-button and continue to create an Office Open XML(.docx)-template. 

Figure 4: DCP Question box

3) The DCP TaskPane opens on the right. Switch to the Template Settings-tab and check the Mark as Label Template-checkbox.
Afterwards click on the [Insert Labels]-button in the www.mscrm-addons.com-ribbon.

Figure 5: DocumentsCorePack TaskPane

4) The Label Options appear. Here, select the required label format and click on the [OK]-button in order to proceed. 

Figure 6: Label Options

5) The selected label format has been inserted to your template. Next, it is important to mark one cell as label-cell. To do so, simply set the cursor in the first cell of the document and click on the [Mark as Label Cell]-button.

Figure 7: Mark label-cell 

6) Once the cell is marked, select a start entity (e.g account) in the TaskPane and insert fields into the label-cell. To do so, please use the fields from the Normal-tab of the TaskPane.

Figure 8: Insert fields into the label-cell

7) Next, you need to define the remaining cells as label-cells as well. To do so, place your cursor in the first cell and click on the [Duplicate Labels]-button. 

Figure 9: Duplicate labels

8) The following information box appears. Click on the [Yes]-button if the cursor is placed in the label-cell.

Figure 10: DocumentsCorePack information box

9) The result looks like this:

Figure 11: Result

10. Now save your template with a click on the [Save Template]-button.

Figure 12: Save your template

How to merge a label template with various records at once

To merge a label template for various records, navigate to Accounts in your CRM system and mark the companies you want to merge. Next, click on the [EXPORT TO WORD]-button in the command bar and select your label template.

Figure 13: Export to Word

The following window appears. Select here, at which position the label should start. 
Insert your start position and click on the [OK]-button. 

Figure 14: Label Options

The result should look similar to the below example. 

Figure 15: Example for merged label template

 

Option B) 

Please note: In General, all Microsoft Word formatting options are supported. However, the label template must be created in advance and saved as .docx!
With option B, it is mantadory to set a regarding relationship when creating the template in advance.  

1) Follow step 1-5 of Option A). Next, switch to the Additional-tab, click on the New Relationship/Entity-drop down menu and click on All Contacts. This makes sure, that the relation is set. 

Figure 16: Make sure that a relation is set

2) Now the relation is set and you can choose the appropriate fields from the DocumentsCorePack Task Pane. Please go on with the step 6 of Option A) and create your template.

4) Once you are finished, please navigate to e.g. the main form of your Account-entity in your CRM system and mark alll contacts that should be displayed on the label. Next click on the [EXPORT TO WORD]-button and select your label template. 

Figure 17: Export to Word

5) Your result could look similar to Figure 18.

Figure 18: Result

For details on how to create label templates with .dot, please click here.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++

           Please note: This article applies to 2015 as well as to CRM 2015/2016

++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This article outlines where to find the version number for each mscrm-addons product. Click the link below for the addon that you wish to find the version number for.

• ActivityTools
• AttachmentExtractor
• DocumentsCorePack ServerBased
• DocumentsCorePack Client
• GroupCalendar
• PowerSearch
• SmartBar
• TelephoneIntegration Server
• TelephoneIntegration Client

ActivityTools

Please note: Because there are two different ways to install and integrate ActivityTools, there are also two ways to verify the 
current ActivityTools version number.  

For 2015: To verify the current ActivityTools version number, start Configuration – ActivityTools for MS CRM 2015 from the StartPane. 

For 2015/2016:

For those who have installed ActivityTools via .exe installer: 

To verify the current ActivityTools version number, start Configuration – ActivityTools for MS CRM 2015/2016 from the StartPane. 

Figure 1: Search for the ActivityTools Configuration

Now the following window appears. It shows the ActivityTools version number (highlighted in yellow) for MS CRM 2015.

Figure 2: Organization overview - ActivityTools

For those who have installed ActivityTools via solution import: 

To verify the current ActivityTools version number, open your CRM Settings and navigate to Solutions:
 

Figure 3: Navigate to Solutions
 
In the solutions, look for the ActivityToolsPluginCore-solution that provides you with the latest version number.
 

Figure 4: ActivityTools version number CRM 2015

Figure 2 and 4 show the latest version number for CRM 2015. 

The version number for MS CRM 2015/2016 is 2015.207.  

AttachmentExtractor

For 2015: To verify the current AttachmentExtractor version number, start Configuration – AttachmentExtractor for MS CRM 2015 from the StartPane. 

For 2015/2016: To verify the current AttachmentExtractor version number, start Configuration – AttachmentExtractor for MS CRM 2015/2016 from the StartPane. 

Figure 5: Search for the AttachmentExtractor Configuration

Now the following window appears. It shows the AttachmentExtractor version number (highlighted in yellow) for MS CRM 2015.

Figure 6: AttachmentExtractor version number CRM 2015
The version number for MS CRM 2015/2016 is 2015.101. 

DocumentsCorePack ServerBased (DCP SB)

For 2015: To verify the current DocumentsCorePack Server version number, start Configuration – DocumentsCorePack for MS CRM 2015 from the StartPane. 

For 2015/2016: To verify the current DocumentsCorePack Server version number, start Configuration – DocumentsCorePack for MS CRM 2015/2016 from the StartPane.  

Figure 7: Search for the DocumentsCorePack ServerBased Configuration

The following window appears. It shows the DCP SB version number (highlighted in yellow) for MS CRM 2015.

Figure 8: DCP SB version number CRM 2015

The version number for MS CRM 2015/2016 is 2015.115.

DocumentsCorePack Client (DCP Client)
To verify the current DocumentsCorePack Client version number, start MS Word, navigate to the www.mscrm-addon.com-tab and click on the [DocumentsCorePack Settings]-button.

Figure 9: Open the DCP settings

In the settings window select the About Documents Core Pack–tab, where the version number is displayed. 

Figure 10: DCP Client version number CRM 2015

The version number for MS CRM 2015/2016 is 7.105.

GroupCalendar

For 2015: To verify the current GroupCalendar (GC) version number, start Configuration – GroupCalendar for MS CRM 2015 from the StartPane. 

For 2015/2016: To verify the current GroupCalendar version number, start Configuration – GroupCalendar for MS CRM 2015/2016 from the StartPane. 

Figure 11: Search for the GroupCalendar Configuration

The following window appears. It shows the GC version number (highlighted in yellow) for MS CRM 2015.

Figure 12: GC version number CRM 2015

The version number for MS CRM 2015/2016 is 2015.101.

PowerSearch

For 2015: To verify the current PowerSearch (PS) version number, start Configuration – PowerSearch for MS CRM 2015 from the StartPane. 

For 2015/2016: To verify the current PowerSearch version number, start Configuration – PowerSearch for MS CRM 2015/2016 from the StartPane. 

Figure 13: Search for the PowerSearch Configuration

The following window appears. It shows the PS version number (highlighted in yellow) for MS CRM 2015.

Figure 14: PS version number CRM 2015

The version number for MS CRM 2015/2016 is 2015.102.

SmartBar

For 2015: To verify the current SmartBar (SB) version number, start Configuration – SmartBar for MS CRM 2015 from the StartPane. 

For 2015/2016: To verify the current SmartBar version number, start Configuration – SmartBar for MS CRM 2015/2016 from the StartPane. 

Figure 15: Search for the SmartBar Configuration

The following window appears. It shows the SB version number (highlighted in yellow) for MS CRM 2015.

Figure 16: PS version number CRM 2015

The version number for MS CRM 2015/2016 is 2015.103.

TelephoneIntegration Server

For 2015: To verify the current TelephoneIntegration Server (TI Server) version number, start Configuration – TelephoneIntegration Server for MS CRM 2015 from the StartPane. 

For 2015/2016: To verify the current TelephoneIntegration Server version number, start Configuration – TelephoneIntegration Server for MS CRM 2015 from the StartPane. 

Figure 17: Search for the SmartBar Configuration

The following window appears. It shows the TI Server version number (highlighted in yellow) for MS CRM 2015.

Figure 18: TI Client version number CRM 2015

The version number for MS CRM 2015/2016 is 2015.102.

TelephoneIntegration Client

To verify the current TelephoneIntegration Client (TI Client) version number, click on the TelephoneIntegration-icon in the taskbar:

Figure 19: TelephoneIntegration Client icon

This action opens the TI Client balloon. The TelephoneIntegration Client version number can be found on the head of the balloon.

Figure 20: TI Client version number CRM 2015

The version number for MS CRM 2015/2016 is 7.103.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This article outlines how to add the TelephoneIntegration [Call Number]-button manually.

Requirements: TelephoneIntegration for MS CRM 2013/2015

Please note: The button created in this example will be visible on the Contact-form for web-clients only.

 

How to add the [Call Number]-button manually?

First, create a new CRM solution (CRM > Settings > Solutions > New). Then, add the entity to which the [Call Number]-button should be added. This can be done by opening the Add Existing-drop-down menu > Entity. (here: Contact)

Figure 1: Create new solution and add drop down menu

In the now appearing dialog, select No, do not include required components.

This is what the result looks like:

Figure 2: Result

At this point, we recommend to do an unmanaged export of this solution (simply to have a backup). 

Once finished, add the following components to the solution (Add Existing > web Resource):

· Web Resource: ptm_CallStart_32x32 
· Web Resource: ptm_TelephoneIntegration_JSLibrary 
· Web Resource: ptm_ti_js_CallButton

Figure 3: Components added to Web Resource

Next, open the RibbonWorkBench and select this solution.

Once loaded, drag and drop a Split Button from the Toolbox to your Form-ribbon.

Figure 4: Drag and drop a Split Button

With a right-click on the Split Button a flyout opens. Make another right-click on the flyout-element Delete.

Figure 5: Split Button flyout menu

Next, define its properties on the right side. Please find a sample below.

· Id: any unique ID (new.contact.Button.form.ptm_tiCallNumberFlyOutCustom)
· Image16by16: select the included :ptm_CallStart_32x32-webresource
· Sequence: position of your button (here: 110)
· Label Text: Any text (here: Call Number)
· ToolTipDescriptionText: any text (here: Use this button to start calling out)
· ToolTipTitleText: any text (here: Call Number)
· All other properties can be left as they are

Figure 6: Split Button Properties

Next right-click on Commands > Add New.

Then select the new command.

Figure 7: Enter new command

Define its properties on the right side.

Id: any unique id (here: new.contact.command.form.ptm_tiCallNumberFlyOutBaseCustom)

Figure 8: CommandDefinition properties

After that, hit the lookup-icon of Actions and in the popping up dialog click on the [Add]-button.

In the next dialog, select Javascript Function Action and click on the [OK]-button.

Figure 9: Add Javascript Function Action

Define the properties of the next dialog like this:

· FunctionName: WriteRegistryBasedCallOutEntity 
· Library: select TelephoneIntegrationJSLibrary (ptm_TelephoneIntegration_JSLibrary)
· Parameters: can be left empty

Figure 10: Define properties 

Click on the [OK]-button to in order to complete the process.

Next, click on the lookup-icon of DisplayRules and the following window will open. Click on the [+Add New]-button.

Figure 11: Display Rules-window

Define a unique ID (here: new.contact.displayrule.form.ptm_tiCallNumberFlyOutCustom) and click on the [Add Step]-button. 

Figure 12: Add new display rule

Select Client Type Rule and continue with a click on the [OK]-button.

Figure 13: Select rule type

In the next dialog specify the following fields:

· Default: False 
· InvertResult: False 
· Type: Web

Figure 14: Specify fields

Finish it with a click on the [OK]-button and then again, click on the [OK]-button.

Now the functionality for the main button is ready.

The next step is to include a command for the population of the flyout-menu. To do so, right-click on Commands > Add New

Figure 15: Include a command

Enter an Id (here: new.contact.command.form.ptm_tiCallNumberFlyOutPopulateCustom)

And hit the lookup-icon(next to Actions)

Figure 16: Define the command properties 

Now add the following Javascript Function Action:

· FunctionName: ptmTICallButton.PopulateItem 
· Library: select ptm_ti_js_CallButton

Figure 17: Add Javascript Function Action

Next, click on Parameters, click on the [Add]-button and add the following types:

· Type: CrmParameter Name: Value: CommandProperties 
· Type: CrmParameter Name: Value: SelectedControlSelectedItemIds 
· Type: CrmParameter Name: Value: SelectedEntityTypeName 
· Type: StringParameter Name: Value: new.contact.command.form.ptm_tiCallNumberFlyOutItemCustom

Finish the process with a click on the [OK]-button and click again on the [OK]-button.

Figure 18: Add types

The next step is creating the final command. It will be executed when a user hits on a flyout-item.

Right-click on Command > Add New

Figure 19: Add final command

Insert the ID new.contact.command.form.ptm_tiCallNumberFlyOutItemCustom and hit on the Actions lookup-icon.

Figure 20: CommandDefininition Properties

In the now popping-up dialog, click on the [Add]-button. Select Javascript Function Action and click on the [OK]-button.

Define the Javascript function properties as follows:

· FunctionName: ptmTICallButton.onClickMenuItem 
· Library: select ptm_ti_js_CallButton

Figure 21: Javascript Command Properties

Next, click on Parameters and click on the [Add]-button. Insert the following types:

· Type: CrmParameter Name: Value: CommandProperties

· Type: CrmParameter Name: Value: SelectedEntityTypeName

· Type: CrmParameter Name: Value: SelectedControlSelectedItemIds

· Type: CrmParameter Name: Value: PrimaryEntityTypeName

· Type: CrmParameter Name: Value: SelectedEntityTypeCode

Figure 22: Define Parameters

Complete with a click on the [OK]-button and then again, click on the [OK]-button.

Back in the main-window of RibbonWorkBench, select the button in the ribbon and choose the recently created commands in the dropdown-boxes Command and PopulateQueryCommand

Figure 23: Select the [Call Number]-button

To complete the button, click on the [Publish]-button.

Figure 24: Publish the button

When you now open a contact record, you will find the [Call Number]-button.

The main button and the flyout should work.

 

 

 

 

 

Figure 25: Published [Call number]-button

The result Xml of the RibbonWorkBench should look like this:

You could try to use this Xml for other entities as well.

For example, you could replace .contact. with .lead. and change the location of the CustomAction

BUT we cannot guarantee that this is working! 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This article outlines how to add the DocumentsCorePack [Export to Word]-button manually.

Requirements: DocumentsCorePack (DCP) for MS CRM 2013/2015

Please note: The button created in this example will be visible on the Account-form for web-clients only.

How to add the [Call Number]-button manually?

 

First, create a new CRM solution (CRM > Settings > Solutions > New). Then, add the entity to which the DCP-button should be added. This can be done by opening the Add Existing-drop-down menu > Entity. (here: Account)

Figure 1: Create new solution and add entity

In the now appearing dialog, select No, do not include required components.

This is what the result looks like:

Figure 2: Result

At this point, we recommend to do an unmanaged export of this solution (simply to have a backup). 

Once finished, add the following components to the solution (Add Existing > web Resource):

· Web Resource: ptm_dcp_icon_exportword16x16 
· Web Resource: ptm_dcp_js_jslibrary 
· Web Resource: ptm_dcp_js_templatebutton

Please note: the Web Resource names above displayed are Name-fields. 

Figure 3: Components added to Web Resource

Next, open the RibbonWorkBench and select this solution.

Once loaded, drag and drop a Split Button from the Toolbox to your Form-ribbon.

Figure 4: Drag and drop the Split Button

With a right-click on the Split Button a flyout opens. Make another right-click on the flyout-element Delete.

Figure 5: Split Button flyout menu

Next, define its properties on the right side. Please find a sample below. 

· Id: any unique id (here: new.account.Button.form.ptm_dcpExportToWordFlyOutCustom)
· Image16by16: select the included :ptm_dcp_icon_exportword16x16-webresource
· Sequence: position of your button (here: 100)
· Label Text: Any text (here: Export to Word)
· ToolTipDescriptionText: any text (here: Starts the document generation of DCP Client)
· ToolTipTitleText: any text (here: Export to Word)
· All other properties can be left as they are

Figure 6: Split Button Properties

Next right-click on Commands > Add New.

Then select the new command.

Figure 7: Enter new command

Define its properties on the right side.

Id: any unique id (here: new.account.command.form.ptm_dcpExportToWordFlyOutBase)

Figure 8: CommandDefinition properties

After that, hit the lookup-icon of Actions and in the popping up dialog click on the [Add]-button.

In the next dialog, select Javascript Function Action and click on the [OK]-button.

Figure 9: Add Javascript Function Action

Define the properties of the next dialog like this:

· FunctionName: DCP.Lib_Registry.printInWord 
· Library: select ptm_dcp_js_jslibrary 
· Parameters: can be left empty

Figure 10: Define properties 

Click on the [OK]-button to in order to complete the process.

Next, click on the lookup-icon of DisplayRules and the following window will open. Click on the [+Add New]-button.

Figure 11: Display Rules-window

Define a unique ID (here: new.account.displayrule.form.ptm_dcpExportToWordFlyOut) and click on the [Add Step]-button. 

Figure 12: Add new display rule

Select Client Type Rule and continue with a click on the [OK]-button.

Figure 13: Select rule type

In the next dialog specify the following fields:

· Default: False 
· InvertResult: False 
· Type: Web

Figure 14: Specify fields 

Finish it with a click on the [OK]-button and then again, click on the [OK]-button.

Now the functionality for the main button is ready.

The next step is to include a command for the population of the flyout-menu. To do so, right-click on Commands > Add New

Enter an Id (here: new.account.command.form.ptm_dcpExportToWordFlyOutPopulate)

And hit the lookup-icon(next to Actions) 

Figure 15: Define the command properties 

Now add the following Javascript Function Action:

· FunctionName: ptmDcpTemplateButton.DynamicMenuDCPTemplate 
· Library: select ptm_dcp_js_templatebutton

Figure 16: Add Javascript Function Action

Next, click on Parameters, click on the [Add]-button and add the following types:

· Type: CrmParameter Name: Value: CommandProperties
· Type: CrmParameter Name: Value: SelectedEntityTypeName
· Type: StringParameter Name: Value: new.account.command.form.ptm_dcpExportToWordFlyOutItem
· Type: CrmParameter Name: Value: SelectedEntityTypeCode
· Type: BoolParameter Name: Value: true

Finish the process with a click on the [OK]-button and click again on the [OK]-button.

Figure 17: Add types

The next step is creating the final command. It will be executed when a user hits on a flyout-item.

Right-click on Command > Add New

Figure 18: Add final command

Insert the ID new.account.command.form.ptm_dcpExportToWordFlyOutItem and hit on the Actions lookup-icon.

Figure 19: CommandDefininition Properties

In the now popping-up dialog, click on the [Add]-button. Select Javascript Function Action and click on the [OK]-button.

Define the Javascript function properties as follows:

· FunctionName: ptmDcpTemplateButton.OnClickMenuItem

· Library: select ptm_dcp_js_templatebutton

Figure 20: Javascript Command Properties

Next, click on Parameters and click on the [Add]-button. Insert the following types:

· Type: CrmParameter Name: Value: CommandProperties

· Type: CrmParameter Name: Value: SelectedEntityTypeName

· Type: CrmParameter Name: Value: SelectedControlSelectedItemIds

· Type: CrmParameter Name: Value: PrimaryEntityTypeName

· Type: CrmParameter Name: Value: SelectedEntityTypeCode

Figure 21: Define Parameters

Complete with a click on the [OK]-button and then again, click on the [OK]-button.

Back in the main-window of RibbonWorkBench, select the button in the ribbon and choose the recently created commands in the dropdown-boxes Command and PopulateQueryCommand

Figure 22: Select the [Export to Word]-button

To complete the button, click on the [Publish]-button.

Figure 23: Publish the button

When you now open a contact record, you will find the [Export To Word]-button.

The main button and the flyout should work.

Figure 25: Published [Export To Word]-button

The result Xml of the RibbonWorkBench should look like this:

Figure 26: Ribbon Work Bench XML

Figure 27: Ribbon Work Bench XML

You could try to use this Xml for other entities as well.

For example, you could replace .account. with .lead. and change the location of the CustomAction

BUT we cannot guarantee that this is working!!!

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This article outlines how to add images, product photos, company logos etc. to MS Dynamics CRM 2011/2013/2015. In our example we add an image to a CRM contact and later on, we add an image to a template.

Requirements: DocumentsCorePack for MS CRM 2011/2013/2015

How to add an image to a CRM contact 

Figure 1: CRM contact with picture.

The added pictures can also be used to create templates with DocumentsCorePack Client to create e.g. a list with full name and picture:

Figure 2: CRM contact list with pictures

Please Note: CRM limits the size of uploaded images to 144x144 pixels. This means the resultion of the inserted image may not be as expected and does not have the same quality as the original uploaded document.

Step-by-step description

1) Open the CRM-contact you want to add the picture to. You can see the MS CRM placeholder image (highlighted in yellow), next to the contact name.
Please note: Images can only be added to the left corner of a form. You can only add one image on the form at a time. For example, if you want to add product pictures, you can only add one picture per form. 

Figure 3: Random contact in CRM.

Figure 4: Different views for the entity Contact.

2) The following window opens, as soon as you click on the placeholder image. 

Figure 5: Placeholder image

3) Browse an image to be inserted to the contact. Click on the [Open]-button to upload the required picture. 

Figure 6: Select picture to be uploaded

4) In the following window, click on the [OK]-button in order to confirm the picture.

Figure 7: Confirm the picture

5) The image has been added to your contact. 

Figure 8: Picture added to contact

Please note: The image size is limited to 144 x 144 pixels. If you upload an image larger than the standard allowed in CRM 2013, it will be automatically scaled.

 

How to add an image to a template

Requirements: DocumentsCorePack Client addon 

1) Open MS Word click on the www.mscrm-addons.com-tab, then on the [Insert MailMerge fields]-button and answer the following question with a click on the [Yes]-button.

Figure 9: Open new template in Microsoft Dynamics CRM 2013

Please note: Up to MS Dynamics CRM 2013, the DocumentsCorePack Task Pane appears. When you open a template in CRM 2015, the DocumentsCorePack Template Designer opens. 

The DocumentsCorePack TaskPane/TemplateDesigner appears. Select the entity for which you want to generate the template for in the TaskPane (see figure 10) or in the TemplateDesigner (see figure 11) (here: Account).

Because we want to generate a list with all contacts from the account MSCRM-ADDONS.com, we switch to the Additional-tab and select All Contacts. 

Figure 10: TaskPane in CRM 2013

Figure 11: Template Designer in CRM 2015

Select a field (here: Full Name) and click on the [Insert]-button in the Task Pane. Click on the [Insert field]-button in the Template Designer. In both CRM versions, he Insert new table-window appears. There, you can modify the table.
In our example, we want to create a table with two columns. (For additional table formatting options, please read our blog article). 

Figure 12: Insert new table

In the first row we insert the Full Name-field with a double click. Next, we want to insert the images we have added before. To do so, click on the Entity Image-field (CRM 2013)/ Default Image-field (CRM 2015) and click on the [Insert]-button-drop down menu or the [Insert field]-button drop down menu. Select the Insert as picture field-option. 

(Please find further information about the [Insert]-button here. For further information on the [Insert fields]-button, click here.)

Figure 13: Insert as picture field option

The mscrm-addons.com placeholder picture appears. You can edit the picture now. 

Figure 14: mscrm-addons.com placeholder 

Now save your template with a click on the [Save Template]-button and test it. If you have not tested a template yet, please read this article first. 

 

However, the result you get is a list with the full names and images of all contacts saved in this account.

Figure 15: Result

Please do not hesitate to contact us, should you require further information or our assistance.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This blog article outlines how to customize the TelephoneIntegration Context Menu to create new activities and/or entities.

Requirements: TelephoneIntegration Client v.6.20 or higher

Examples: There are several CRM-functionalities available in the context menu of a phone call.

• Per default, the following Activity Types are available as CRM standard:

 
Figure 1: Standard Activity type in the context menu of TI Client.

• But you can expand the default by creating custom activities, like for example Create Lynch Chat and Create Campaign Response.

Figure 2: Custom entity types in the context menu of TI Client.

 

How to create custom activites and/or entities 

To create a new custom activity and/or entity, you have to add a new Settingskey. To do so, please open your CRM and navigate to Settings. 

Figure 3: Open settings

In the settings, double-click on TelephoneIntegration.

Figure 4: Select TelephoneIntegration

In the main navigation section at the top, click on the TelephoneIntegration drop-down and select the MSCRM-ADDONS.COM Settingskeys.

Figure 5: MSCRM-ADDONS.COM Settingskeys

In the next window, click on the [+ADD NEW MSCRM-ADDONS.com Settingskey]-button. 

Figure 6: [+ADD NEW MSCRM-ADDONS.com Settingskey]

Next, type in following:
- Name*: customentities.xml (This is the key value Name)
- IsCached*: Yes
- KeyValue: see figure 7, 8 and 9

Figure 7: SettingsKey - General window

Figure 8: Key value - enlarged

Figure 9: Key value - explained 

 

Custom Entities KeyValue:

In order to create custom entities, please use the following KeyValue. This example shows the KeyValues for Goal and Currency. 

customentities.xml

<?xml version="1.0" encoding="utf-8"?>
<customentities>
    <transactioncurrency>
        <displayname>Currency</displayname>
        <phonefield>currencyname</phonefield>
    </transactioncurrency>
    <goal>
        <displayname>Goal</displayname>
        <phonefield>title</phonefield>
    </goal>
</customentities>

 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This article contains a compatibility chart for all our addons for Microsoft Dynamics CRM 2015. It shows which of our addons are compatible with

• MS Dynamics CRM 2015 On-Premise/Hosted (IFD)/Online
• MS SharePoint 2010/2013/Online
• MS Office (x86, x64) 2007/2010/2013
• and which of them support cross-browsing.

Last Update  December 2015

BETA Version

Last Version-Release Date

MS Dynamics CRM 2015

MS SharePoint

MS Office (x86, x64)

On-Premise

Hosted  (IFD)

Online

Cross Browser

2010

2013

online

2007

2010

2013

ActivityTools

2015.0 and higher

12/02/2014

yes

yes

yes*3)

yes

AttachmentExtractor

2015.1 and higher

12/05/2014

yes

yes

yes

yes

yes

yes

yes

DocumentsCorePack

Server: 2015.4 and higher Client: 7.2 and higher

12/05/2014 12/05/2014

yes

yes

yes

yes*1)*2)

yes

yes

yes

yes

yes

yes

GroupCalendar

2015.2 and higher

12/05/2014

yes

yes

yes

yes

PowerSearch

2015.1  and higher

12/05/2014

yes

yes

yes

yes

SmartBar

2015.1 and higher

12/05/2014

yes

yes

yes

yes

TelephoneIntegration

Server: 2015.1 and higher Client: 7.0 and higher

12/05/2014 12/05/2014

yes

yes

yes

yes

yes

yes

yes

*1) At the moment, FileExplorer-documents, SharePoint-documents and the Document Summary are not compatible.   

*2) All browser windows created by the client application will open in the InternetExplorer. The Server Side will use the current browser.  

 *3) Since version 2015.116.    
    

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.