- Blog


This blog is deprecated since July 2020.The articles below are no longer maintained and might contain outdated information. 
You can find the most acutal and relevenat information in our Knowledge Base at Blog


Hello and welcome to our blog! What can we do for you? Are you looking for further technical information or step-by-step instructions to our products? Or would you like to read the latest news on mscrm-addons? Please feel free to browse our blog for detailed information and to share our posts!

How to enable debugging for PowerSearch

Please note:
This article applies to PowerSearch in MS Dyn CRM 2015/2016.

How to activate debugging via the Settingskeys 
Step-by-step description

Navigate to Settings in Microsoft Dynamics CRM.

Figure 1: MsDynCRM Settings 

In the Settings, select Products in the extension area.

Figure 2: Settings extension

This action will open a list of active Products. Select PowerSearch with a double-click.

Figure 3: Select PowerSearch

In the so opened window, look for debugPlugin.

Figure 4: PowerSearch debugPlugin

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

Figure 5: Set the KeyValue

If no setting with this name is found, you have to create a new Settingskey. To do so, please click on the drop-down-button next to PowerSearch in the CRM ribbon and select MSCRM-ADDONS.COM Settingskey.
In the so opened window, click on the [+ADD NEW Settingskey]-button.
Figure 6: Add new settingskey

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

Figure 7: Newly created settingskey

Step-by-step description on how to acces the log files

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

Figure 8: Advanced Find

Open the Advanced Find. Select the Debug-entity and include the following condition Name must Contain PTMPowerSearch. This ensures that only PowerSearch log files will be retrieved. Then click on Results.

Figure 9: Configure Advanced Find

The following window opens.

Figure 10: Edit Columns window

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

Figure 11: Add Columns window

Back in 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 Export Debug.

Figure 12: Select the debug file by the created on-date

In the next dialog, check Static worksheet ... and press the [Export]-button.

Please send the excel log-file with a short error description and a screenshot to our support address

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to

Comments are closed.