This blog article explains how to build an address block and format it properly with DocumentsCorePack for MS CRM 2013 templates (.docx). With the DocumentsCorePack Field Properties-functionality, users can easily format every address line and define specific line behaviour if the information was not stored in CRM.

Requirements: DocumentsCorePack (DCP) for MS CRM 2013

Example 

Figure 1: DocumentsCorePack String properties-functionaltiy.

How to build an address block

An address block can easy be created with the DocumentsCorePack Template Designer. To do so, open MS Word and navigate to the www.mscrm-addons.com-tab. Click on the [Insert MailMerge Fields]-button and answer the question in teh DocumentsCorePack Question box with a click on the [Yes]-button in order to get to the DocumentsCorePack Task Pane. 

Figure 2: Open the DocumentsCorePack Task Pane.

Figure 3: DocumentsCorePack Task Pane for MS CRM 2013

Once you have selected the Entity Type to work with (here: Account), you can start to insert the proper MailMerge Fields to your future address block. To do so, double-click on the required field to insert it into the document. 

Figure 4: Example address block

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

Figure 5: Save the template.

In the next window, define a name for the template e.g. Accounting_AddressBlock and click on the [Save]-button in order to continue.

Figure 6: Save Template-window

Once your template is saved, select the appropriate CRM Data with a click on the [Choose CRM Data]-button. In the so opened window, type in the Name of the entity you are looking for and click on the

-button in order to look for it. Select the right result with a click on it, so it is highlighted in blue. Next, click on the [Select]-button in order to continue. 

Figure 7: Select the appropriate CRM data

Figure 8 shows a possible result after the document merge, while figure 9 shows the mailmerge fields of the template. 

Figure 8: Merged address block

 

 
Figure 9: Inserted Mailmerge Fields

As you can see, there is several address information missing, because the specific data has not been saved previously in CRM.
In order to format the address block properly, click in one of the fields and then on the [Field properties]-button to define what should happen if the information was missing in CRM.
The String Properties-window will pop up.

Figure 10: String Properties-window.  

Now you can select between two different field options. 

Figure 11: String Properties - window 

• Activating the first chechbox will: delete the line/row if the whole line/row is empty. 
  If the whole line is empty after the merge process, then the whole line will be deleted.

Please note: all characters like hyphens, colons, commas as well as words or additional text (e.g. version #: <>) are also counted as signs. Because of that, the whole line will not be deleted. In this case you have to select the second option.

• Activating the second checkbox will: delete the line/row if the selected field is empty.
  If you select <> and activate this checkbox the line will be deleted if there is no postalcode stored in the chosen record. No matter if there is still data information in the remaining line.

Addional formatting information:
We recommend to activate the Show/Hide formatting marks symbol 

.Figure 12: Paragraph marks and other hidden formatting symbols This is very useful to show paragraph marks and other hidden formatting symbols. 

Figure 13: Activate the “Show/Hide” formatting marks symbol

In order to avoid line distance, users can press [Shift] + [Enter]. 

Figure 14: Avoid line distance with [Shift] + [Enter]  

In this case the line ends where the Show/Hide formattings marks symbol is placed. Then the two lines are joined together and will be treated as one line/row. E.g if you mark the <> content control and click on the second checkbox, <> as well as <> will be deleted.

To learn more about how to remove blank lines except for address blocks, please read our blog article about the DocumentsCorePack Insert Remove Empty Line-button.

 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 (DCP) [Create Document]-button for MS CRM 2011 to your form. 

Requirements: DocumentsCorePack for MS CRM 2011, Ribbon Workbench for CRM 2011

To add the button, you must install the Ribbon Workbench for CRM 2011. (which can be downloaded here) 

Please find the manuals here:

• Getting started with the Ribbon Workbench
• Video: Ribbon Workbench for Dynamics CRM 2011

 

Result: Once added, the [Create document]-button looks like shown in Figure 1. 

Figure 1: [Create Document]-button added to the account entity

How to add the DocumentsCorePack [Create Document]-button

First, open CRM and create a new solution. To do so, please navigate to Settings > Solutions. Name the solution as you wish. 

Figure 2: newly created solution form

Once saved, the form will reload. Click on the [Add Existing]-button and Entity.

Figure 3: [Add Existing]-button

In the next window, select the entity to which the DCP-Button should be added (here: Account). Then click on the [OK]-button. 

Figure 4: Select the enitity to which the button will be added

On the next page select the No, do not include required components-option and click on the [OK]-button.

Figure 5: Missing Required Components-window

Next, click on the [Add Existing]-button again. But this time, please select Webresource.

The window that pops up now will show you all installed webresources. Select ptm_Icon16x16, ptm_Icon32x32 and ptm_dcp_js_jslibrary. 

Figure 6: Select web resources

Figure 7: Select web resources

Your solution window will look like shown in Figure 7. 

Figure 8: Finished solution in CRM.

Next go to the solution section of CRM again. We recommend to create a backup. To do so, mark your newly created solution and click on the [Export]-button.

Figure 9: Create a solution backup in CRM

Click through the dialog. Please note: It is of utmost importance that you select Unmanaged on the last page. 

Figure 10: Export Solution – Webpage Dialog

Click on the [Export]-button in order to proceed. 

Now you can start to create the button.

In the solution-section of CRM, double-click on the RibbonWorkbench-solution. 

Figure 11: Ribbon Workbench-solution

Now the Ribbon Workbench opens. First, select the solution you have created before (which contains the entity and the DCP web resource). 

Figure 12: Ribbon Workbench

The loaded RibbonWorkBench will look like shown in Figure 12:

Figure 13: Loaded Ribbon WorkBench

Now select Form in the dropdown-box in the right upper corner.

Thereafter, select Group and drag and drop it to any place on your form. 

Then select the newly added group in the form. Please find its properties on the right side. You can assign a specific ID to your group. 

Figure 14: Assign a specific ID

Now add a button to your group, again via drag and drop.

Change the ID, select your images and name it.

Figure 15: Define your settings

Next, add the command of the button. Right-click on Commands > Add new. 

Figure 16: Add the command of the newly created button

On the right-side, you can see all properties of the new command. We recommend to give it a meaningful ID.

Then hit on the lookup-field next to Actions. In the window that pops up now, click on the [Add]-button. 

Figure 17: Click on the [Add]-button

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

Figure 18: Select type of rule

In the FunctionName-type in DCP.Lib_Registry.printInWord and for Library select ptm_dcp_js_jslibrary. Click on the [OK]-button. 

Figure 19: Actions-dialog

Back in the WorkBench, mark your button, to see its properties on the right side.

For Command select the newly created command via the ID. 

Figure 20: Mark your button and select its properties

Now that the configuration is done, click on the [Publish Solution]-button in order to import and publish the new solution containing the button.

Figure 21: Publish the new solution

After the process has been finished, your button will be available and ready to use on the Accounts form. 

Figure 22:[Create Document]-button added to the account entity

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

This blog article explains how to install DocumentsCorePack for MS CRM on a terminal server for CRM Online. 

Requirements: DocumentsCorePack

When installing DocumentsCorePack on a terminal server for CRM Online, you have to provide your Login Credentials for the initial installation. Enter a valid username and password.
Next, modify the registry. This ensures that other users are able to create a connection with their own login credentials easily when they start using DocumentsCorePack for the first time on the terminal server. 

Figure 1: Enter login credentials

Then please run regedit in the StartPane. 

Figure 2: regedit in the Start Pane

Now browse to HKEY_LOCAL_MACHINE\SOFTWARE\PTM EDVSysteme\ and select the configured profile (you can see the profile used in the HKLM\SOFTWARE\PTM EDV Systeme\DocumentsCorePackclient2011\ActiveProfileSetting).

Depending on the architecture of your server (x86 or x64), the location may vary. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PTM EDVSysteme\ -> If this node is present please also perfrom the following modification for these registry keys.

Figure 3: Registry Editor 

Next, select the correct profile and search for the CrmUserName key. 

Figure 4: Registry Editor I

Now change the existing key from your actual username to e.g. EnterYourUsername@mw.onmicrosoft.com. It is important that the domain is still the same as for your login. 

Figure 4: Registry EditorII

Your new profile should now look like this: 

Figure 5: New profile

If now a different user logs on for the first time on the server, he will be presented with  this dialog as soon as he tries to use DocumentsCorePack. The user can then enter its own user specific credentials.

Figure 6: Dialog appears when a different user logs in for the first time on a terminal server using DCP.

Please note: These steps will only work, if the actual users do not have an actual profile yet, which is only the case on initial installation.

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 hide the [Create Document]-button for specific entities.

Requirements: DocumentsCorePack ServerBased (DCP SB)

At the moment we only have the possibility to hide the button for specific entities. To do so, please create a new settingskey for AutoMerge as described here. Please name it AMCreateDocumentButtonEntities.

This is a comma-seperated list of entities e.g. account,contact,lead etc.

You could also specify to show the button only on the grid or only on the form for each entity. E.g. account,contact|grid,lead|form to show it on the account grid and form, for the contact only in the grid and for the lead only on the form.

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 SmartBar in MS CRM 2013, 2015, as well as to MS CRM 2015/2016.

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

Basically, there are two possibilities to enable debugging:

Solution 1) Activating debugging by using the SmartBar Settings (recommended way, only if the SmartBar Settings doesn’t work, use the second solution).

Solution 2) Activating debugging manually via MSCRM-ADDONS.com Settingskeys

 

Solution 1) How to activate debugging by using the SmartBar Configuration, step-by-step description

Open the Settings of SmartBar for MS CRM 2013. Please note, that only the users owning at least one of the selected SecurityRoles listed in the SmartBar Config, are able to see the Settings-Icon. Please find the button that opens the settings in the SmartBar ribbon.

Figure 1: Settings of the SmartBar Dialog highlighted in green

This action will open the SmartBar Settings. There, select the General Settings-tab and enable debugging.

Figure 2: Enable debugging in the SmartBar Settings

If debugging is enabled, hit the [Save]-button. Now debugging is activated. Please scroll down and read detailed information on how to access the log files.

Solution 2) HOW TO: activate debugging manually via the MSCRM-ADDONS.com Settingskeys step-by-step description

In CRM navigate to Settings.

Figure 3: Settings in CRM

In the settings, select MSCRM-ADDONS.com Products in the Extension area. 

Figure 4: the MSCRM-ADDONS.com Products in the Extension area. 

This action will open a list with all active MSCRM-ADDONS.com Products. 

Figure 5: Active MSCRM-ADDONS.com Products in CRM.

Next, select SmartBar with a double-click on it. In the next window search for debugPlugin.

Figure 6: SmartBar debugPlugin

If a result is found, double click on it and set the KeyValue on true.

Figure 7: SmartBar debugPlugin - general information.

If no setting with this name is found, you have to create a new Settingskey. To do this, please click on the drop-down-button next to SmartBar in the CRM ribbon and select MSCRM-ADDONS.COM Settingskey. 

Figure 8: Settingskey in the CRM ribbon

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

Figure 9: Add a new Settingskey to CRM

Now create a new Settingskey with the following value and save your settings. 

 

Figure 10: New MSCRM-ADDONS.com Settingskey
 

SOLUTION 2) How to acces the log files, step-by-step description 

The log files will be stored in the MSCRM-ADDONS.com Debug-entity. The easiest way to access it, is by using the Advanced Find.

Figure 11: Advanced Find in CRM 

This action will open the Advanced Find. There select the MSCRM-ADDONS.com Debug-entity and include the following condition Name must Contain PTMSmartBar. This ensures that only SmartBar log files will be retrieved. Then hit the [Results]-button.

 
Figure 11: Advanced Find window in CRM.

The editor displayed in Figure 12 opens. 

Figure 12: Edit Columns functionality

Use the Add Columns-functionality and add the ptm_message-field to the grid. Press the [OK]-button in order to continue.

 
Figure 13: Add columns

Back to the main dialog, click on the [Results]-button.

Next, delete all retrieved debug records. Another way is to select the debug file by the Created On-date. Then reproduce the error and refresh the result list of this Advanced Find. This ensures that you only have the latest and relavant log files. Select all records and hit the [Export MSCRM-ADDONS.com Debug]-button. 

Figure 14: [Export MSCRM-ADDONS.com]-button in CRM Advanced Find

In the next dialog check “Static worksheet ...” and hit the [Export]-button. 

Please send the excel log-file with a short error description and a screenshot to support@mscrm-addons.com

This article outlines how to prepare DocumentsCorePack (DCP) for MS CRM 4 for an upgrade to CRM 2011 or CRM 2013!

Requirments: DocumentsCorePack 

1) Export your templates from CRM 4
Please open the DocumentsCorePack Server Config in the Start Pane. In the General Settings-tab, click on the […]-button and save a copy of the saved templates folder.

Figure 1: General Settings-tab

2) Uninstall DocumentsCorePack in CRM 4.
Before you can upgrade your CRM 4 to 2011 or 2013 version, you must uninstall the 3rd party addons and check that all buttons that have been deleted.
After the migration, you can then install the latest version of each addon. If you skip this step, it is more complicated to get rid of the buttons and icons before you can install the CRM 2011 addons.

For further information, please read our blog article Upgrading CRM 4 to CRM 2011 with 3rd party addons.

3) Upgrade CRM
You can upgrade your CRM system now.

4) Install DocumentsCorePack for MS CRM 2011 or 2013
Next, install DocumentsCorePack for MS CRM 2011 or 2013 in the newly upgraded CRM environment.

5) Apply your 2011 or 2013 licenses
DCP for MS CRM 2011 or 2013 requires a new license. Make sure you have a valid addon-license for MS CRM 2011 or 2013.
Please note: Your actual DCP for MS CRM 4 license is not valid for 2011 or 2013. If you have a valid support contract, then you can order the new CRM 2013 license for free. For further information, please contact our support-team to get your new license and install it with the LicenseManager. 

6) Import Templates
Once the valid license is installed, import your templates into the new 2013 environment using the DocumentsCorePack Configuration utility. For more information, please read our blog article DocumentsCorePack for MS CRM 2013: How to import/export Templates. Now you can test your imported templates. If everything works correctly, go on to the next step.

7) Uninstall DocumentsCorePack Client for MS CRM 4 from the Client machine
To uninstall DocumentsCorePack Client for MS CRM 4 select Programs in the ControlPanel. Search for the DocumentsCorePack Client for MS CRM 4 in Uninstall or change a program. Follow the instructions to uninstall the DocumentsCorePack Client.

8) Re-Install 2011 or 2013 DocumentsCorePack Client on Client machines

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 integrate new entries in the SmartBar entity and SiteMap entry search field.

Requirements: SmartBar for MS CRM 2013

Example:

Figure 1: SmartBar Entity and SiteMap Entry search field.

If you have added entities or sitemap-entries to your CRM organization after the installation of SmartBar for MS CRM 2013, they won't be available in the entity-search box of SmartBar. Please follow the steps below to integrate them.

1) Open the MSCRM-ADDONS.com Products overview in CRM
First, open the SmartBar dialog at the top of any CRM entity window. Then type in Products to get to the MSCRM-ADDONS.com Products-overview. 

Figure 2: SmartBar search field.

This action ópens the Active MSCRM-ADDONS.com Products-overview. 

Figure 3: Active MSCRM-ADDONS.com Products-overview

Next, select SmartBar with a double-click.

2) Delete the CBEntities-Settingskey
In the next window, search for the CBEntities-Settingskeys and delete it. 

Figure 4: SmartBar Settingskey

3) Restart the SmartBar Config
Now restart the SmartBar Config in the StartPane. 

 

Figure 5: SmartBar Config

Select your profile to connect to the organization for which the entities have been added. Select the appropriate organization and click on the [OK]-button. 

Figure 6: CRM Connection setup window

As soon as the connection and user rights have been verified, select the appropriate organization and click on the [Launch Config.]-button.

Figure 7: Organization overview for SmartBar for MS CRM 2013

This action will open the SmartBar Server Config.-window. As soon as this window has been loaded, the process is completed. Now click on the [OK]-button in order to finish. 

Figure 8: SmartBar Server Config. for MS CRM 2013.

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

This article outlines where to find the Settingskeys for our products in MS CRM 2013/2015.

Example:

Figure 1: TelephoneIntegration Settingskeys in CRM.

 

To get the Settingskey, open your CRM-System and go to Settings > MSCRM-ADDONS.com products.

Figure 2: Settings > MSCRM-ADDONS.com Products

This action opens the following window. 

Figure 3: Active MSCRM-ADDONS.com Products

Select the required product with a double-click to get to the Settingskeys. (Here: TelephoneIntegration)

Figure 4: TelephoneIntegration Settingskeys

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

Generally, TelephoneIntegration allows users to dial from related CRM-records. But users also have the possibility to set restrictions for the related records to be displayed in the TelephoneIntegration balloon. This means that they have the possibility to select from a list of records related to the initially opened one when dialing out from CRM (e.g. from related leads, contacts, etc.).

Requirements: TelephoneIntegration

           

Figure 1: Outgoing call from an opportunity without restrictions, displaying all available related phone numbers.

       
Figure 2: Outgoing call from an opportunity with restrictions, not displaying related contacts and leads.

In order to set restrictions, you have to create a new settingskey for TelephoneIntegration. 

1. To create a new settingskey, follow the steps in this article.

2. Insert the following structure for your new settingskey:

Name*: DFR_Disable_{entity name}
KEyValue: entity name1;entity name2; entity name3
Furthermore, set IsCached as yes 

In our example (dialing out starting from an opportunity, accounts should be displayed, but not the related contacts and leads), we have to type in the following structure:

< DFR_Disable_opportunity, contact;lead >

Figure 3: Newly created settingskey

If you want to disable all subrelated data records (meaning that you do not want any related record to be displayed), you have to insert a * into the KeyValue-field and DFR_Disable_opportunity into the Name-field.

3. Result

If you now call out from Opportunity, the TI balloon will only display accounts, but not the related contacts and leads.

Figure 4: Opportunity

Figure 5: Outgoing call from an opportunity with restrictions, not displaying related contacts and leads.

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

The Lead Qualifier Plugin is a small solution that changes the process of creating a contact and account from the information within a lead. The main difference to the out-of-the-box-solution for this scenario within CRM 2013 is that no opportunity is automatically created within the process. 

This allows CRM users to qualify a new lead at any time during the CRM working process. Moreover, the plugin allows the association of the lead to already existing contacts or accounts in addition to creating new entities of said types, which saves time and avoids duplicates. 

Figure 1: Qualify Lead-dialog box

The LeadQualifier plugin v1.0.1 comes with all solutions needed to work properly. Click here for free download! 

The Lead Qualifier solution can be installed like any other solution via Settings > Customizations > Solutions. 

Figure 2: Solutions in CRM 

How to use the Lead Qualifier Plugin, step-by-step descpription

First open your CRM-system and select any entity you want to work with e.g. Test TestContact1. Click on the [QUALIFY]-button at the top of the form. 

Figure 3: Active lead within CRM which we want to qualify for

The Qualify Lead-window appears. 

Figure 4: Qualify Lead-window

 

 

Using the email adress provided in the lead, the following steps are carried out:

1. Find the exact email address in existing contacts. Please note: The following email domains will be ignored during the search, as they are too general and will lead to incorrect results. (This often concerns online email hosters). 

• gmail
• yahoo
• mail.ru
• hotmail
• trash-mail
• mailtrash
• mailinator
• freemail
• rediffmail
• mail2000
• citromail
• maildistiller
• damailbox

2. Find accounts associated with exact matches from step 1

3. If no exact matches are found in step 1, the Qualify Lead-plugin will search for email addresses in the contacts that contain the domain-part of the leads' email address. (here: TestCompanyABC.com)

4. From the matches found in step 3, this plugin will find the associated accounts and add them to the suggested accounts drop down box. 

Figure 5: account that is associated with contacts with a similar email adress.

5. If an existing account/contact is found within CRM, you can click on the […]-button in order to open that entity in a new tab/window (see Figure 5). 

6. If none of the searches returns any results (either for contacts or accounts)m then the respective drop down box remains empty and only the Create new contact-option is available.

7. After making the selections and clicking on the [OK]-button, the correct account and contact are opened (newly created or existing, depending on selection made in the dialog) and the entities are associated in the correct fashion. The information available in the lead is also transferred to these entities.

Figure 6: The related account and contact of the lead have been opened in CRM.

If existing contacts or accounts have been previously associated with the lead (e.g. by using the Existing Contact/Account?-fields) then these are added and pre-selected in the respective drop-down boxes, even if they would normally not have been found by the email-based search.

Figure 7: Predefined contact

The plugin replaces the standard [Qualify]-button within CRM 2013 (both, in the Lead Form and the Leads Grid View).

Figure 8: modified mscrm-addons.com CRM[QUALIFY]-button 

Due to the nature of the plugin (using a dialog), the possibility of qualifying multiple leads from the grid view is disabled. The [QUALIFY]-button within the lead form and the lead list view uses the same process. 

Figure 9: A single selection makes the[QUALIFY]-button visible.

Figure 10: Muliple or no selection makes [QUALIFY]-button ivisible.

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