This blog article outlines how to execute an additional "Attach document"-operation by checking the Run workflow checkbox in the DocumentsCorePack Dialog (highlighted in yellow below). Therefore you have to create a workflow, which will then be displayed in the Run workflow drop-down menu. 

More information about how to create a workflow can be found here. 

Figure 1: DocumentsCorePack Dialog - Run workflow

  

Within this tutorial, we will create such a workflow step-by-step. The result will be a document which will be ❶ attached to an e-mail and also ❷ attached as a note as you can see in the figure below.

Figure 2: The result

Please open your Microsoft Dynamics 365 and navigate to Settings > Processes. In the My Processes - area, click on the [New]-button in order to create a new workflow.  A dialog pops up. Type in ❶ the name of your workflow, determine ❷ an entity - MSCRM-ADDONS.com AutoMergeWorkingItems in this case and select ❸ Workflow as the process category. Afterward, hit the [OK]-button. 

The window below pops up, where you can configure your workflow in detail. Please check the ❶ As an on-demand checkbox in the Available to Run-area and as Scope select ❷ Organization. Next, please add a new step by hitting on the [Add Step]-drop-down menu and select ❸ Create Record. 

As soon as the step has been added to your workflow, please enter ❶ a name that remains you of what it contains, e.g. Attach note. Then open the drop-down menu, select ❷ MSCRM-ADDONS.com AutoMergeWorkingItems and hit the ❸ [Set Properties]-button. 

The dialog below opens. It allows you to configure your workflow. Again, give it a ❶ name - Attach a note in this case and select ❷ AttachToEntity in the AutoMergeAction-field. Next, set the cursor in the ❸ PrimaryRecordUrl-field and select ❹ PrimaryRecordUrl in the drop-down menu in the Form Assistant, click on the [Add]-button and hit the [OK]-button below (highlighted in yellow). The PrimaryRecordUrl-field is filled now. Do the same for the ❺ EntityToAttach (RecordURL(Dynamic)). Then, set the cursor in the ❻ DocumentGUID-field, select CreatedDocument in the Form Assistant and proceed like before. To finish the workflow, please do not forget to click on the ❼ [Save and Close]-button. 

After finishing the configuration, do not forget to activate your so created workflow by hitting the [Activate]-button located at the top. 

To see the result, please open the DocumentsCorePack Dialog by hitting the [Create Document]-button in your Dynamics 365. As shown in the first figure, the dialog ❶ attaches the document as an email attachment and by checking the ❷ Run workflow checkbox you can start the so created workflow and also attach it as a note. 

​

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 handle the CRM Sandbox Plugin errors.

Long loading time of add-ons
ActivityTools, PowerSearch, and SmartBar use a CRM sandbox plugin in the background. It is a known CRM problem that the first plugin execution could take very long. Unfortunately, it is beyond our control. More information can be found here. 

If you have not used the add-on for a long time or the handler opens a new worker process this can happen. But if you use the add-on frequently (like in a production environment), the plugin will stay cached and this initiation should not happen very often. 

If you load the add-on a few times after each other (independent if it is for the same record or not), at least from the 7th execute on it should be normal fast. Based on our information CRM starts 6 worker process maximum. The 7th execute will use one of the existing. 

But that it can take longer to load than a default CRM field is normal because add-ons get started on page load. At this time CRM internal components are almost finished. 

 
Communication object error
If ActivityTools, SmartBar, PowerSearch or the license information request the configuration page fails, a red error message will be displayed. If it contains the following message, it indicates that anything is not correct with the CRM Sandbox service. 

Mesasge: System.ServiceModel.Security.SecurityNegotiationException: Microsoft Dynamics CRM has experienced an error.

How to solve for NOT CRM online organizations: 
Go to the CRM Server (in case of multiple servers to the backend server) -> Services Look for "Microsoft Dynamics CRM Sandbox Processing Services" and restart it. 

Figure 1: Look for “Microsoft Dynamics CRM Sandbox Processing Services”

If this should still not work, please check the Sandbox service configuration as shown in this article. In many cases, a wrong or not set SPN is the reason for the issue. 

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

​

​

This blog article outlines how to proceed if you get the following error message in your web browser: "Resource not found for the segment ‘ptm_......’.

A full error message can look like this: 
Error from FetchWebApi: Ressource not found for the segment ‘ptm_mscrmaddons_keies’

We have only experienced this problem for OnPremisse installation so far. 

The problem is, that the EntitySet property of our custom entities is not correct. Normally a manual reimport of the correct CRM solution with the option "Overwrite Customizations" can fix this. 

How to fix for OnPremise installations

• Navigate to the machine on which the Server part of the add-on is installed. 
• Open the installation directory  (per default: "C:\Program Files (x86)\PTM EDV-Systeme GmbH\[PRODUCT NAME] Server for Microsoft Dynamics 365") -> subfolder "essentials"
• If your CRM version is 9.0 or higher open the subfolder "9.0",  for 8.2 versions stay in the "essentials" folder 
• Open a web browser: Dynamics 365 -> Settings -> Solution -> hit "Import"
• Now select the correct solution from your current directory (depending on the error message):
  • MSCRMADDONScomGeneral.zip for
    • “ptm_mscrmaddons_keies”
    • “ptm_mscrmaddons_schedulers”
    • “ptm_mscrmaddons_settingses”
    • “ptm_mscrmaddonscom_debugs”
    • “ptm_mscrmaddonscommetadatas”
    • “ptm_mscrmaddonstemps”
  • DocumentsCorePack.zip for 
    • “ptm_mscrmaddons_dcptemplateses”
  • AutoMergeServerCore.zip for 
    • “ptm_automergeworkingitemses”
    • “ptm_mscrmaddonscomamtriggers”
  • For different resources please contact our support

• The wizard will tell you that the same version of this solution is already installed. If the versions are different it could be possible that you have selected the wrong solution file! 

Figure 1: Solution information

 

• Check "Overwrite customizations" and follow the wizard below. 

Figure 2: Overwrite customizations 

• The problem should be solved now. 
  
  

Sample
Error message: Resource not found for the segment ‘ptm_mscrmaddons_keies’
CRM version: 8.2
Installed product: DocumentsCorePack 

To Solve: 
Reimport the solution "MSCRMADDONScomGeneral.zip" of the folder "C:\Program Files (x86)\PTM EDV-Systeme GmbH\DocumentsCorePack Server for Microsoft Dynamics 365\essential". 

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

​​

This blog article outlines how to act if you are facing the checkin/checkout issue when uploading documents to SharePoint via DocumentsCorePack. To be more specific - you have enabled the versioning in SharePoint but DocumentsCorePack is creating new documents every time instead of updating the existing ones. The documents are getting generated without versioning instead it is creating new documents with la el suffixed as (1).  

For example:
Test Document
Test Document(1)
Test Document(2)

That´s because of per default our DocumentsCorePack does not support versioning on SharePoint. To activate versioning, please make sure that you are using the latest version DocumentsCorePack, which can be found here and enable the 2 settings displayed in the figure below.

To do so, please open your Dynamics 365, navigate to Settings and select DocumentsCorePack. In the General Settings-tab please scroll down to the SharePoint Settings-area and enable the two settings highlighted in yellow.  

Figure 1: DocumentsCorePack General Settings

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

This blog article outlines that it is possible to use non-interactive users to create services for our add-ons. Please find more information about how to set up the online service configuration for our solutions by using the links below:

• AttachmentExtractor: step-by-step tutorial, video
• DocumentsCorePack: step-by-step tutorial, video

As you may know, a non-interactive user is not a typical user, it is more an access mode that is created with a user account.  A non-interactive user account does not require a Dynamics 365 license and can be used to set up services for our add-ons. 

More information about how to create a non-interactive user account and how to assign online security roles can be found in the corresponding Microsoft Dynamics 365 guide. 

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 check the installation status on Microsoft AppSource. For example, if you started the installation of GroupCalendar form Microsoft AppSource. At a later time, you want to check if the installation is completed or if there were any problems. This article explains how this can be done.

First, go to the Microsoft 365 Admin Center. Within Dynamics 365 hit on ❶ "Navigate to other applications" and hit ❷ "Admin". 

Figure 1: Microsoft 365 Admin Center

Next, please navigate within Microsoft 365 admin center to the section "Admin centers" as you can see below. 

Figure 2: Admin Centers

In the so opened management console select the correct ❶ organization and hit on ❷"Solutions". 

Figure 3: Dynamics 365 management console (in the German language here) 

Next, please select the product for which you want to get more information - in this case, GroupCalendar.

Figure 4: Installation status of GroupCalendar

This blog article outlines how to activate the Unified Interface module view via TelephoneIntegration Client. The Unified Interface for Dynamics 365 is an updated interface for all devices accessing Dynamics 365. For a brief overview of the new interface and what can users expect, please have a look at this short video. 

How to activate the Unified Interface 
For activating and choosing your desired Unified Interface, please open the TelephoneIntegration Client Settings, navigate to ❶ Advanced and choose your module in the ❷ Unified Interface ID area. The default value is None. After choosing the Module and saving the setting, the new Dynamics 365 records and activities will pop up with that view. 

Figure 1: TI client advanced settings

This year, PTM EDV-Systeme GmbH is celebrating its 20th year as a high-quality software solution provider. We thank our clients, employees, and partners for their contributions to our continued success.

Celebrating 20 Years of PTM EDV-Systeme GmbH

The year 2018 marks our 20 Year Anniversary since the business was established back in 1998 located in Graz/Austria. Since the founding of our business in 1998, the world has changed a great deal and we developed two major business areas: 

• PTM EDV-Systeme GmbH  - development of customized software
  With the help of individual and innovative solutions that are optimally custom-built, we wanted to fulfill our customer´s requirements. We started to realize projects independently and on our own, delivering and implementing the finished solution at our customer´s site.
  Nowadays we are able to support customers in the following fields of application, using our know-how and our customized software solutions: software development, system migrations, interface problems between hardware and software, the adaption of Microsoft Dynamics 365 etc.
  
  

• MSCRM-ADDONS.COM - addons for Microsoft Dynamics 365
  In 2004, we started to develop and support addons for Microsoft Dynamics 365. Our innovative solutions closed gaps existing in the standard Dynamics 365 platform and extended it with useful functionalities. Nowadays our products allow a more efficient use of Dynamics 365 within your company as they enable more fluent and quicker Dynamics 365 processes and a better overview. 

To celebrate this important achievement, a spectacular trip to Palma de Mallorca, Spain was organized for our employees at the beginning of October. There is no better town for a team building event like Mallorca - the vibrant city reflects the spirit of Spain like no other. This trip also was a good way for our team to get more connected and work better together. 

The past 20 years have been amazing. We’ve been humbled by how our technology has been adopted, and by you — our amazing customers, partners, and friends — who’ve helped us out so much along the way. Thanks for taking a moment to celebrate with us, and we look forward to many more years of working together with you!

To all our past and current clients and partners: THANK YOU for keeping us in business for 20 years. Look for our solutions and blog articles in which we’ll continue to share the wealth of knowledge and experience you helped us acquire.

Your PTM (mscrm-addons.com) team 

This short blog article outlines how to search for the internal value of an option field. 

The selectable options from option fields always consist of two values, a display value and an internal value. 

For example: 

• Field: Status
• Display Values: Active, Inactive
• Internal Values: 0, 1
  
  

Option 1: Build the desired filter in the advanced find in Dynamics 365 and download the fetchXML. You will now see the internal value, highlighted in red as you can see in the figure below - Active=0

Figure 1: Download the fetchXML

Option 2: Navigate to Dynamics 365 > Settings > Customization and select Customize the System > [Your Entity] > Fields > [Your Field]

You can take a look at the properties of this field there and check the internal and display values of all available options. 

Figure 2: Field properties 

 

Update:  To test the compatibility of your phone system, please download the Phone Test Tool. A sptep-by-step user guide is in the ZIP-file included. The tool offers two commmunication channels (TAPI and SIP). You need only one of them to be able to use our CTI addon. 

The goal of that blog article is to describe how to easily test whether TelephoneIntegration addon would work with customer PhoneSystem (PBX) either over TAPI or over SIP. This is the easiest 5 minute testing without any deep technical knowledge about TAPI or SIP.

Prerequisites & Checklist

1) Details of phone system:
a. Vendor name:
b. Model name:

2) Is a TAPI driver available for your phone system ? (yes/no)
If you are unsure, please check with your phone system vendor for availability. 

3) If #2 is no: Is your phone SIP-based? (yes/no)
If you are unsure, please check with your phone system vendor for details. 

4) Depending on Have you been able to verify compatibility using the information below? 

Compatibility tests:

In order to make the most out of the call please ensure that a person with rights to download/install software as well as a person familiar with the phone system is available during our call OR has been able to perform the below tests prior to our joint call. 

 TAPI-driver available for your phone system:

1. After installing and configuring the TAPI – driver for your phone system
2. Start Window Phone Dialer by pressing “Win+R” to call out the Run box, then type “dialer.exe” and hit Enter.

Figure 1: Window Phone Dialer - Run box

3. Type in the number you want to dial and then go to Tools and select Connect Using as you can see in the figure below.

Figure 2: Phone Dialer


4. Choose your TAPI line and press the [OK]-button. In this case, it is 3 CX TAPI line, but in yours, it might be something different. 

Figure 3: Choose the TAPI line

5. Press Dial. You should see a new Dialing popup as you can see below.