This article describes how to send emails in workflows with dynamic images. Sometimes, it happens that e-Mail programs do not resolve inserted dynamic images correctly. With our DocumentsCorePack [Insert as Picture-Link]-field you can solve this problem.

First open a template or create a new one with the email content. Then insert the dynamic image into the document.

There are two different ways to insert dynamic images in a Word Template (docx.):

1) Insert picture as “Base64String”
Then the picture will be inserted in the email content as picture. This is set in Word as default. Sometimes it happens, that email programmes do not resolve these pictures correctly when sent.

2) Insert picture as a “Link”
With the “Insert as Picture-Link-Field”-functionality users are able to insert a picture directly from a link which is stored in any CRM-field! Available for DocumentsCorePack v5.97 and higher. Click here for download and test it. For more information on how to insert a Picture-Link-Field to your template please click here for a step-by-step description. Please note, that the recipient needs to access the picture externally.

Enable Word properties to use picture link
As default, Microsoft Words properties are set to always insert picture as “Base64String”. Which means that the picture will be inserted in the email content as picture. Sometimes it happens, that email programs do not resolve these pictures correctly when sent. In order to enable MS Word inserting a picture link in your template, follow the instructions below (valid for Word 2013):

In your opened docx.template go to “File”

Figure 1: Click on FILE

and click on “Info”. Then choose “Properties” and “Advanced Properties”

Figure 2: Click on INFO

In the following window, switch to the “Custom”-tab:

Figure 3: MS Word Properties Window

Set the “Name:” as “AlwaysExportImagesAsBase64” and set the “Value:” to “false”. Then click on "Add" and click “OK”. 

Note: You have to enable this property for every Template for which you want to insert dynamic images. Now, Picture-Link-Fields can be inserted into your Template (.docx) and resolved correctly. 

Once finished, save your template.

Next create or open an appropriate email-workflow and upload your template. As a result, the picture has been added as a picture link and the email programm is able to resolve it correctly when sent. (See next screenshot)

Figure 4: Picture in an email body which has been inserted as picture-link-field

Next open your CRM and navigate to an entity e.g. “Account” “MSCRM-ADDONS.com”. Click on the “more commands”-sign at the top to start a workflow. 

Learn how to create a workflow here. 

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 a document and attach it to an email in a single AutoMerge workflow-step for MS CRM 2013 Online.

First open your CRM and go to “Settings” > “Processes” and create a “New” workflow: 

Figure 1: Create new workflow 

In the next window type in a “Process Name” e.g. “Test_Workflow”, choose the “Entity” for which you want to create the workflow for e.g. “Account”. Set the “Category” to “Workflow” in order to create a new workflow process. Click on “OK” to confirm. 

Figure 2: Create a new process

First, the email has to be created. Therefore click on the “Add Step”-drop-down-button and choose “Create Record”. Type in a name for your step e.g. “Create Email” and set the “Create:” to “Email”. Then click on “Set Properties”.

Figure 3: create a record in AutoMerge Workflows.

An email activity opens. In this window, a sender, a subject and an email text has to be defined. Set the cursor in the “Recipient”-field to define the recipient. To do so, select “Look for: Account” in the “Form Assistant”-area on the right sight, click on “Add” and then on “OK”. Now the “Recipient”-field is filled out correctly. Follow the same instructions for the “Regarding”-field, in order to set the regarding entity. E.g: “Account”. 

Figure 4: window to configure an email activity.

Click on “Save and Close”.

The second step would be to create a new MSCRM-ADDONS.com AutoMerge Working item, where the document is generated and attached to the email. To do this, add a new step with click on “Add Step” and choose “Create Record”. Type in a step description and set “Create:” to “MSCRM-ADDONS.com AutoMergeWorkingItems” 

Figure 5: Add a MSCRM-ADDONS.com AutoMerge Working item.step

Click on “Set Properties”. In the next window type in a name and define the AutoMerge-action. E.g. “CreateDocument”. It it important to insert the “PrimaryRecordsUrl”. For that, set the cursor in the “PrimaryRecordUrl”-field and go to the “Look for:”-area within the form assistant on the right side and select “Record URL(Dynamics) from the second drop-down-menu, click on “Add” and “OK”.

To determine the Template to be executed, set your curser in the “TemplateToExecute” field and look for it. Next to this, a file format has do be defined. E.g “pdf”. In the “TemplateToExecute”-field search for the document that should be attached. E.g. “Account_Overview_DOCX.docx”. Next set the cursor in the “EmailToAttach”-field and go to the “Look for:”-area within the form assistant on the right side and select “Create Email (Email)”. Click on “Save and Close”. (See next screenshot)

Figure 6: workflow-step configuration. E.g. Create and attach a document to an email message.

Now your workflow is finished and ready to be used. The possible result could look like this:

Figure 7: Shows email workflow with pdf-document attached. Click to enlarge.

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

This article describes how to solve the description field problem in DocumentsCorePack. If you try to create an activity and it fails with the soap Exception you see below, it is due to the limitation of length of the “CRM description-field”. 

Figure 1: SOAP EXception error.

There are three possibilities to solve this problem:
1) By customizing the “letter”-entity
2) By disabeling DCP description
3) By cutting the DCP description


1) Customize “letter”-entity
To do this, open CRM, click on "Settings" ---> "Customizations" ---> “Customize the System”.  

Figure 2: Customization in your CRM system.

In the next window, search for the entity “lettter” in the tree view on the left, chose “Fields” in the drop-down list and scroll down to “description”. (See next screenshot)

Figure 3: Description field in CRM 

Open “description” with a double-click. Now you can change the value of the field “Maximum Length”. (See screenshot below)

Figure 4: Description of letter

Next, click on “Save and Close”. Once you changed the value, click on “Publish All Customizations”.

Figure 5: Save, close and publish your customizations

2) Disable DCP description
The second option would be, disabeling DCP description. This can be done by a new "Settings-key" for DocumentsCorePack. (Possible since DCP Client v4.53). Learn how to create a new Settingskey here. 

Name the new settingskey "DoNotFillDescriptionField", set “IsCached” with “No” and give it a value "true" (field blank) and “Save” your settings. 

Figure 6: New settingskey settings

Now you have disabled the DocumentsCorePack description field.

3) Cut DCP description
The third option would be by cutting the DCP description. The number of character is either the same (in our example its “2000”) or smaller than the actual length attribute. For example if you type in a value of “1000”, then “1000” character will be filled into the description field and the rest is cut.

This can be done in the products settings key. Follow the steps described in the second option, to generate a new settings key. Set the name with “DoNotFillDesciptionField”, set “IsCached” with “No” and give it a value “1000” and “Save” your settings. (See next screenshot).

Figure 7: Cut the DCP description

Now you have set the option to only show 1000 signs and cut the rest.

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

This article outlines how TelephoneIntegration Client works with Outlook client. Available for TelephoneIntegration Client v5.54 and higher.

TelephoneIntegration can popup CRM forms also in Outlook client instead in Internet Explorer browser.

This feature is activated with a CRM server-side settingkey.
(For detailed information, please read more about "Using TelephoneIntegration for MS CRM 2013 for Outlook only: http://mscrm-addons.com/post/2014/01/27/Using-TelephoneIntegration
-for-MS-CRM-2013-with-MS-Outlook-only.aspx

Using TelephoneIntegration for MS CRM 2011 for Outlook only: http://blogs.mscrmaddons.com/post/2013/04/03/Using-TelephoneIntegration
-with-MS-Outlook-only.aspx  )

Please note, that TelephoneIntegration client is not accessing the Outlook client over any API, since Outlook does not provide suitable API interfaces.

It is simply opening the Outlook client process with a parameter that resembles a CRM entity URI.

For example, the following URI address represents a PhoneCall URL in an online CRM organisation

https://pkdemo12.crm4.dynamics.com/main.aspx?etn=phonecall&pagetype=entityrecord&extraqs=phonenumber%3D0321321

In the past the TI client opened the form in Internet Explorer by calling the iexplore.exe process with the URL address as parameter.

C:\Program Files\iexplore.exe URL

C:\Program Files\iexplore.exe

https://pkdemo12.crm4.dynamics.com/main.aspx?etn=phonecall&pagetype=entityrecord&extraqs=phonenumber%3D0321321

Instead of passing the URL to iexplore.exe process, we pass it now to outlook.exe process

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office 2013\outlook.exe URL

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office 2013\outlook.exe

https://pkdemo12.crm4.dynamics.com/main.aspx?etn=phonecall&pagetype=entityrecord&extraqs=phonenumber%3D0321321

You can verify this by simply starting Command Prompt window and starting the Outlook client with CRM URL record.

Attention!

Customized CRM Ribbons might interfere with the way outlook opens CRM Related URLs via external calls (As we open the CTI windows). If you face troubles of that kind, please contact your Microsoft support, as the ribbon integration is beyond our control.

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

This article describes, how to use TelephoneIntegration for MS CRM 2013 with MS Outlook only. Users have the possibility to use TelephoneIntegration without a browser, but with Outlook only, meaning that TelephoneIntegration will open all windows (e.g. the CRM-call-activity, etc.) in Outlook and not in an internet browser window.

For being able to use TelephoneIntegration with Outlook only, you have to install TelephoneIntegration Client v.5.54 or higher (click here to download the latest version) and to create a new settingskey . Please follow the steps below to do so.

1. Open your CRM in the Internet Explorer

2. Navigate to the CRM Settings

3. Choose ‘MSCRM-ADDONS.com Products’ from the ‘Extensions’ in the Settings menu.

Figure 1: MSCRM-ADDONS.com Products in the CRM Settings

4. (1) Click the checkbox in front of ‘TelephoneIntegration’ and then click on ‘Edit’. Now create a new settingskey for TelephoneIntegration. Learn how to create a new settingskey here. 

Figure 2: Edit TelephoneIntegration in the CRM Settings

5. Name the settingskey ‘UseOutlookOnly’ and the KeyValue ‘true’. Furthermore, set ‘IsCached’ as ‘yes’. 

Figure 3: Create new settingskey

After that, you have to restart the TelephoneIntegration client. To do this open it with right click on the TelephoneIntegration Client Sign in the Taskbar and close it with right click! Afterwarts search for “TelephoneIntegration Client” in your Start menu and restart the Client again.

Figure 4: Restart TelephoneIntegration Client Icon (to be found in the Taskbar)

From now on, TelephoneIntegration will open all windows in Outlook and without using a browser.

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 configure unmanaged entities for SmartBar for MS CRM 2013!

Requirements: SmartBar for MS CRM 2013, v2013.4 and higher. All our addons come with an unlimited 14-day free trial. Please click here to download and test it!

To successfully enable SmartBar for MS CRM 2013 for unmanaged entities, please follow the instructions listed below: 

1 Step: Enable SmartBar (SB) for the custom entity
This can be done by enabling the checkbox of the SmartBar Server Config. Open your SmartBar Server Config from the Start menu. Check the unmanaged entity in the Server Configuration window and save your settings. 

2 Step: Open Customizations within CRM
Then open CRM and navigate to "Settings" and click on “Customizations” (see next screenshots).

Figure 1: Navigate to Customizations in your CRM 

Next click on “Customize the System” 

Figure 2: Click on Customize the system 

3 Step: Open the entitiy’s main form:
In the next window open the “Main”-Forms of the entity in the tree view on the left. This example is for the entity “Account”.

Figure 3: The Main-form of the entity account. 

This action will open following window:

Figure 4: Form Properties of the entity account. 

In this new window click on the “Form Properties”-button. This will open the “Form Properties – Webpage Dialog” 

 

Figure 5: The Form Properties – Webpage Dialog

4 Step: Add SmartBar library in the “Form Libraries”-section
This can be done by clicking on the [+Add]-button in the "Form Properties -- Webpage Dialog" and selecting the “ptm_SmartBar/js/OnLoadCommandBar.js"-web resource. (See next screenshot)

Figure 6: Add Smart Bar library

5 Step: Focus the “Event Handler”-section
Ensure that the “Control”-list box is set to “Form” and “Event” to “OnLoad”. Then click on the [Add]-button. The following window will appear:

Figure 7: Event handler-section

In this window, select the “ptm_SmartBar/js/OnLoadCommandBar.js”-library and fill in “ptm_SmartBarStart” in the textbox next to “Function”. Ensure that “Enabled” is checked. (See screenshot above).

To finish, please click on [OK] and [Save] and [Publish] the customization. (See next screenshot).

Figure 8: Save and publish your customizations

NOTE: When you chose to uninstall the product, those links have to be removed manually als well. They do not harm the CRM but will redirect to dead links if you leave them in place.

Result:
As a result the number of related entities is now displayed in the bracket. (See next screenshot)

Figure 9: The result

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

This article outlines additional formatting options for splitting a tables header or footer.

Requirements: DocumentsCorePack (DCP) for MS CRM 2013, v6.11 and higher. All our addons come with an unlimited 14 days free trial. Please click here to download and test it!

With DocumentsCorePack for MS CRM, tables can easily be inserted in Word and merged with data from CRM. This is very useful for e.g. displaying a list with product information. Therefore click on “Insert MailMerge Fields” and select a type e.g. “Quote”. Then go to the “Additional”-tab in the “DocumentsCorePack Task Pane” and click on “Quote Products”. 

Figure 1: “Additional”-tab in DocumentsCorePack Task Pane 

This action will give you the look-up field:

Figure 2: The look-up field for “Quote Product”.

With a double click on a field, following window appears:

Figure 3: The display and formatting options for tables.

With the new feature you can split a tables header and/or footer. Just activate the checkbox Split header or Split footer and define how many columns shoud be created. The value goes from 1 up to 63. E.g. we want our table to be displayed with a header and 5 columns. The result looks as follows:

Figure 4: Create table with header and 5 columns 

Now you can add some additional information:

 

Figure 5: Insert additional information 

 

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

This article outlines the formatting options for number and money-fields within the “Insert Computed-field”-function (.docx).

Requirements: DocumentsCorePack for MS CRM 2013, v6.11 and higher. All our add-ons come with an unlimited 14 days free trial. Please click here to download and test it!

The “Insert Computed-Field”-button allows you to make basic arithmetical operations with CRM-number and –money-fields. Click here for more information about this functionality.

Once you have finished, click into your ‘Computed Field’ and click on “Field properties” in the ‘'www-mscrm-addons.com”-ribbon at the top. See next screenshot:

Figure 1: Open the field properties

Following window appears:

Figure 2: The field properties of the computed field.
In this window, fields can be changed and an optional name can be defined. By clicking on [Change Format] following window appears: 

Figure 3: Set field properties

Type – this shows the inserted field type.
Name: this shows the name of the inserted field.
Example: this shows the actual display field format. 
Type – click on the drop down button to choose from different display options.
(See next screenshot, click to enlarge)

Figure 4: Field properties - type

Culture: this shows the culture format.

Figure 5: Field properties - culture

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 configure a workflow with AutoMerge for Microsoft Dynamics CRM 2013 Online. The steps described below solely refer to AutoMerge for MS Dynamics CRM 2013 Online. For details about how to create a workflow with AutoMerge for MS Dynamics CRM On-Premise, please watch our demonstration videos on our YouTube channel. (Click here to watch the videos)

How to create a workflow with AutoMerge for Microsoft Dynamics CRM 2013 Online:
First of all, start in the settings of your CRM system and click on ’Processes’ in the Ribbon. (See screenshots below) 

 
Figure 1: Open Settings>Processes

Following window appears:

Figure 2: Processes-area in CRM settings

Then click on ‘New’ to create a new workflow. A webpage dialog pops up. Type in a name, determine an entity and choose ‘Workflow’ as the process category. Afterwards, click on ‘OK’.

Figure 3: Webpage dialog to create a new workflow/dialog.
After clicking on ‘OK’, you will see the following window. Start to define and add the steps you would like to have in your workflow. If you would like to e.g. create the document as a first step of your workflow, click on the ’Add Step’-drop-down menu and select ‘Create Record’.


Figure 4: Window for workflow-configuration.

Now, the first step is added to your workflow. Type in a description of the step, e.g. create document. Afterwards, open the drop-down menu within this first step, select ‘MSCRM-ADDONS.com AutoMergeWorkingItems’ and click on ‘Set Properties’. 

Figure 5: window for workflow configuration, creation of first workflow-step ‘CreateDocument’

The following window will open to configure the first step of your workflow. Type in a name and define the AutoMerge-action. In our example, we select the action ‘CreateDocument’.

Figure 6: window for workflow-step configuration, definition of a name and of the AutoMergeAction ‘CreateDocument’.

After that, choose the template to be used within the workflow (see screenshot ellipse 1) and the file format the document should be saved as (see screenshot ellipse 2).

Furthermore, it is very important to insert the ‘PrimaryRecordUrl’. For that, set the cursor in the ‘PrimaryRecordUrl’-field and go to the ‘Look for’-area within the form assistant on the right side. Select ‘Record URL(Dynamics)’ from the second drop-down-menu (see screenshot below, ellipse 3 and 4), click on ‘Add’ and then on ‘OK’. After that, the ‘PrimaryRecordUrl’-field is filled out automatically. (see screenshot below, colored in yellow) Click on ‘Save and Close’.

Figure 7: window for workflow-step configuration, definition of the template to be used in the workflow, the file format the document should be saved as and the PrimaryRecordUrl.

Figure 8: window for workflow-step configuration, configuration of first workflow-step finished.

The first step of your workflow is now added and fully configured. In case you want to stop your workflow at this point, you can click on ‘Save and Close’ and finish here. In case you want to add further steps to your workflow, define a condition to be fulfilled before adding further steps. For example, if you want to create a letter-activity with the previously generated document as an attachment, you need to make sure that the document creation is completed before attaching the document to the letter activity. To do so, open the ‘Add-Step’ drop-down menu again and select ‘Wait Condition’. (S

Figure 9: window for workflow configuration, ‘Wait condition’-step added.

The step is added to the workflow. Type in a step description and click on ‘ (click to configure)’. 

Figure 10: window for workflow configuration, ‘Wait Condition’-step added.

After that, a window pops up. In this window, you can define the condition to be fulfilled for workflow proceeding. In our case, we select ‘Create document (MSCRM-ADDONS.com AutoMergeWorkingItems)’ from the first drop-down menu, ‘Status’ from the second drop-down menu, ‘Equals’ from the third drop-down menu and ‘Inactive’ from the fourth drop-down menu. (see screenshots below). Click on save and close. Now, you have determined that step 2 of your workflow (in our example to attach the created document to a letter-activity) will only be executed if the first step, namely the document generation, has finished successfully.

Figure 11: window to configure ‘Wait Condition’-step

Figure 12: window to configure ‘Wait Condition’-step

Afterwards, your workflow configuration will look like in Figure 13.

Figure 13: window for workflow configuration, ‘Wait condition’-step added and configured

To add another step, e.g. to create a letter-activity, click on ‘Select this row and click Add Step’ (see screenshot ellipse 1) and afterwards on ‘Add Step’. 

Figure 14: window for workflow configuration, add workflow-step 2 ‘letter’

Then, select ‘Create Record’ from the drop-down menu. The new step is now added to your workflow and ready for configuration. Type in a step description (e.g. Attach document to letter), open the drop-down menu within this second step and select ‘Letter’. 


Figure 15: window for workflow configuration, workflow-step ‘letter’ added. Click to enlarge.

Afterwards, click on ‘Set Properties’ and a letter-activity-window will open. Within this window, define a sender, a subject and type in your letter-text. Then, set the cursor in the ‘Recipient’-field to define the recipient. To do so, go to the ‘Look for’-area within the form assistant on the right side. Select ‘Account’ in both drop-down-menus, click on ‘Add’ and then on ‘OK’. Now the ‘Recipient’-field is filled out correctly.

Figure 16: window to configure letter-activityClick on ‘Save and Close’. Now you are back in the general workflow-window again and you can see the added and completely configured letter-activity. In a next step, you have to define that the previously created document should be added to this letter-activity. For that, click on ‘Add Step’ and select ‘Create Record’ from the drop-down menu. 

Figure 17: window for workflow configuration, add ‘AttachToLetter’-step.

Type in a step description and open the drop-down menu within this step. Select ‘MSCRM-ADDONS.com AutoMergeWorkingItems’. Then, click on ‘Set Properties’.

Figure 18: window for workflow configuration, add ‘AttachToLetter’-step.A window will pop up to configure the ‘AttachToLetter’-workflow-step. Put a name and define the AutoMerge action (in this example choose ‘AttachToLetter’, see screenshot, ellipse 1) Within the ‘Attach to Letter’-section, determine the letter-activity to which the created document should be attached to (see screenshot ‘LetterToAttach-field, ellipse 2) and the document which should be attached (see screenshot ‘DocumentGUID_Letter’-field, ellipse 2).

Figure 19: window to configure workflow-step, configure ‘AttachToLetter’-step.

For determining the letter-activity the document should be attached to, set the cursor in the ‘LetterToAttach’-filed in the ‘Attach To Letter’-area (see screenshot, ellipse 1) and select the correct letter-activity from the drop-down menu in the ‘Look For’-area within the form assistant on the right side. (See screenshot, ellipse 2). After that, click on ‘Add’ and ‘OK’.

Figure 20: window to configure workflow-step, configure ‘AttachToLetter’-step. 

To determine the document to be attached, set the cursor in the ‘DocumentGUID_Letter’-field (see screenshot, ellipse 1) and select the correct document from the drop-down box in the ‘Look For’-area within the form assistant on the right side. (See screenshot, ellipse 2) Click on ‘Add’ and ‘OK’.

Figure 21: window to configure workflow-step, configure ‘AttachToLetter’-step.

You have now completed the configuration of this step. Click on save and close. In case you want to stop your workflow at this point, you can click on ‘save and close’ within the general workflow-configuration-window and finish here. In case you want to add further steps to your workflow, you have to define a condition to be fulfilled before you add further workflow-steps. In that case, open the ‘Add-Step’ drop-down menu again and select ‘Wait Condition’. Click on ‘ (click to configure)’ and a window will pop up. In this window, define which condition has to be fulfilled for further workflow proceeding. In our example, we want the workflow to proceed when the created document has been attached to the letter-activity. In our case, we select ‘Attach document to letter step 2 (MSCRM-ADDONS.com AutoMergeWorkingItems)’ from the first drop-down menu, ‘Status’ from the second drop-down menu, ‘Equals’ from the third drop-down menu and ‘Inactive’ from the fourth drop-down menu. (See screenshots below). Click on ‘Save and Close’.

Figure 22: window to configure ‘Wait Condition’-step.

Now you can add another workflow-step. In our example, we want the document to be deleted after it has been attached to the letter-activity. To do so, click on ‘Select this row and click’ and open the ’Add Step’-drop-down menu. Select ‘Create Record’. Afterwards, type in a step-description, choose ‘MSCRM-ADDONS.com AutoMergeWorkingItems’ from the drop-down box within the step and click on ‘Set Properties’. A window will pop up in which you can determine that the created document should be deleted after it has been attached to the letter-activity. For that, put a name and an AutoMerge activity (in our example ‘DeleteTempDocument’). Afterwards, click in the ‘DocumentGUID_Delete’-field within the ‘Delete Temp Document’-area (see screenshot, ellipse 1) and select the document to be deleted from the drop-down box in the ‘Look For’-area within the form assistant. (See screenshot, ellipse 2).

Figure 23: window to configure workflow-step, configure ‘Delete Temp Document’-step.

Click on ‘Save and Close’. After that, you have finished your workflow configuration and you can click on ‘Save and Close’.

Figure 24: window to configure workflow, workflow-configuration finished.

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

The following table shows the different culture information for displaying the DATETIME() function for DocumentsCorePack templates (.docx).