News.mscrm-addons.com Blog

How to bypass the IFD authentication for GroupCalendar

Wed, 16 Nov 2016 12:13:51 GMT

Please note: This article is for users with very good CRM skills only.
However, before you follow the below instructions, please contact us via support@mscrm-addons.com.

1) In order to bypass the IFD authentication, you need to edit the ptm_WebApplicationPreloaderGeneralScript webresource in Dynamics 365.

2) Look for

appUrl = SetQueryString(appUrl, "isOutlook", $ptm.isOutlook + '');

and replace it with

appUrl = SetQueryString(appUrl, "isOutlook", $ptm.isOutlook + '');

var userIDCrm = $ptm.context.getUserId();

if ((userIDCrm == null) || (typeof (userIDCrm) == "undefined")) {

userIDCrm = parent.Xrm.Page.context.getUserId();

}

appUrl = SetQueryString(appUrl, "ORIFDI", userIDCrm + '');

3) Next, save your changes and publish them.

4) Open your IIS. In there, turn on Anonymous only and add a CRM system administrator to this authentication mode.

5) Restore the original WebConfig and WebApplication Port and change the Connection Profile for the tool to OnPremise.

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

DocumentsCorePack FileExplorer in IFD environment

Mon, 01 Feb 2016 15:42:00 GMT

This article is about the DocumentsCorePack (DCP) FileExplorer in IFD environments for CRM 2011, 2013, 2015 and 2016.

Basically, DocumentsCorePack's FileExplorer is not supported in CRM IFD environments. Nevertheless, it could be possibly working. If you want to try to configure it, follow this article.

Limitations

The embedded File Explorer only works in Internet Explorer (does not work in any other browser and is not tested with MS Edge).
FileExplorer won’t work when accessing CRM from outside the local network.
When launching FileExplorer with the IE-Dev-Tool opened, you will notice a security warning regarding to mixed http and https.
There is no further development planned!
In combination with IFD, FileExplorer integration is not covered by the support contract.

Steps to configure

These steps have to be performed after the default installation of DocumentsCorePack Server part without any special configurations (do NOT run the IFD tool for DCP).

Change the connection type of the DCP profile to 0:
Open the registry of your CRM server > Local Machine > Software > PTM EDV-Systeme > AutoMergeServer > ActiveProfile

Figure 1: Registry editor
Look for the connection-profile with this ID in Profiles and set CrmConnectionType to 0.

Figure 2: CrmConnectionType
Internet Information Services Settings
The DCP-Website must have an http-binding including a free port. To ensure that, open the IIS Manager and select the DocumentsCorePackserver-website and check the bindings. Remember the port: Its value will be required in the next steps.

As well in IIS Manager, ensure that the Managed pipeline mode of the DocumentsCorePackserverPool- Application Pool is set to Classic:

Figure 3: Edit Application Pool
Navigate to CRM > Settings > MSCRM-ADDONS.com Products and open DocumentsCorePack. In the below grid, all settingskeys will be listed.
For DCP File Explorer only, follow A. If you also use DCP Server based (e.g. CRM workflows) to store documents to the FileShare, follow B.
1. Open the WebApplicationPort-setting and change its KeyValue to assigned port of the DCP Website.
  
  Figure 4: WebApplicationPort
  
  And Open “DCPServerUrl” and change its “KeyValue” to “http://+[CRM server URL]:
  
  Figure 5: DCPServerURL
2. Open WebApplicationPort-setting and change its KeyValue to “http://+[CRM server URL + Port of website in IIS] +/fileexplorer/fileexplorer.aspx?testp=|”:
  
  Figure 6: Define the WebApplicationPort KeyValue
  
  And Open DCPServerUrl and change its KeyValue to http://+[CRM server URL]:[port of DCP website]:
  
  Figure 7: Define the DCPServerURL KeyValue
  
  Please note: The [OpenDocument]-button is NOT supported in this case!
Define Server-based user (only necessary if you use DCP ServerBased)
Go to CRM > Settings > Solutions > and open AutoMergeServerCore. Its ConfigPage will load. Use it to define a user which have enough permission to access the file share and CRM (in doubt, a local and CRM admin).

Figure 8: DCP Server-based Config
Permission: Give everyone full access on the file share and its sub folders (required).
Define a user which is a CRM admin and local admin in the DCP webconfig. To do so, open the DocumentsCorePack web.config-file of the installation directory (usually C:\Program Files\PTM EDV-Systeme GmbH\AutoMerge Server for MS CRM 2015\web.config) and modify the identity-node:

Figure 9: web.config-file of the installation directory
Make the website work within CRM: Open the InternetExplorer settings and allow mixed content.

Figure 10: InternetExplorer Settings

Trouble Shooting

This error could appear when you open the website:

Figure 11: Server Error in '/' application

To resolve it, open the web.config of the installation directory of DCP Server part and remove both lines starting with Infragistics2. In addition, change the targetFramework of compilation to 4.0 (if not already done).

This error could appear when you try to save files to FileShare:

File is not saved to file share.

Activate debugging of DCP FileExplorer (see Solution 2: SERVER SOLUTION): link
If generating documents via DCP server based (e.g. from a CRM Workflow), activate server based debugging as well: link
You can find the log-files in the subfolder Log of the installation directory of DCP Server part.

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

Our addons compatibility with Dynamics CRM 2015, SharePoint and MS Office

Fri, 05 Dec 2014 14:19:00 GMT

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^*3)

yes

AttachmentExtractor

2015.1
and higher

12/05/2014

yes

DocumentsCorePack

Server: 2015.4
and higher
Client: 7.2
and higher

12/05/2014
12/05/2014

yes

yes^*1)*2)

yes

GroupCalendar

2015.2
and higher

12/05/2014

yes

PowerSearch

2015.1
and higher

12/05/2014

yes

SmartBar

2015.1
and higher

12/05/2014

yes

TelephoneIntegration

Server: 2015.1
and higher
Client: 7.0
and higher

12/05/2014
12/05/2014

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.

Certificate Changes in an IFD environment

Thu, 26 Jun 2014 16:22:00 GMT

This blog article explains what to do if one of the certificates has changed in the IFD environment. If so, our products require additional steps in order to work again.

This issue can occur with two different certificates:

1) SSL certificate
2) Token Signing certificate

1) How to react in case of the SSL certificate

First of all, you need to rerun the IFD-wizard and select the correct certificates (since in the web.config your old certificates are still cached).

Figure 1: Certificates in AD FS

Next, please update the Relying Party Trust with the new Federation Meta Data URL which has been created in the IFD Wizard previously.

If this does not work correctly, you will need to delete and recreate the relying party trust for our product on the ADFS Server.

Then, specify the Federation Metadata URL, which was created by the IFD Wizard and click on the [Next]-button.

Figure 2: Specified Federation Metadata URL

Next, please specify a display name and click on the [Next]-button.

Figure 3: Specified display name.

Then check the Permit all users to access this relying party-option and click on the [Next]-button.

Figure 4: Permit all users to acess this relying party

Please check if everything looks alright and then click on the [Next]-button.

Figure 5: Check changes

After you have finished working with the Add Relying Party Trust-Wizard, the Rules Editor appears.
There, click on the [Add Rule]-button.

Should the Editor not open automatically, please right-click the relying party object you have created before in the Relying Party Trust list, click on the [Edit Claims Rules]-button and then click on the [Add Rule]-button.

Please note: It is of upmost importance that the Issuance Transform Rules-tab is selected. In the Claim rule template list, select Pass Through or Filter an Incoming Claim template and then click on the [Next]-button.

Create the following rule:

Claim rule name: Pass Through UPN (or something descriptive)
Add the following mapping:

1. Incoming claim type: UPN

2. Pass through all claim values

Click on the [Finish]-button.

In the Rules Editor, click on the [Add Rule]-button and in the Claim rule template list, click on Pass Through or Filter an Incoming Claim Template. Click on the [Next]-button in order to proceed.

Claim rule name: Pass Through Primary SID (or something descriptive)
Add the following mapping:

1. Incoming claim type: Primary SID

2. Pass through all claim values

Click on the [Finish]-button.

In the Rules Editor, click on the [Add Rule]-button.

In the Claim rule template list, select Transform an Incoming Claim Template and then click on the [Next]-button in order to continue.

Now create the following rule:

Claim rule name: Transform Windows Account Name to Name (or something descriptive)
Add the following mapping:

1. Incoming claim type: Windows account name

2. Outgoing claim type: Name

3. Pass through all claim values

Click on the [Finish]-button and as soon as you have created all three rules, click on the [OK]-button in order to close the Rules Editor.

2) How to react in case of the Token Signing certificate

Figure 6: Certificates in ADFS

Please replace the old thumbprint of the Token Signing Certificate in the web.config with the thumbprint from your new Token Signing Certificate. As soon as you have replaced it, click on the [OK]-button in order to proceed.
Please note: Do not copy the thumbprint from here, type it of instead (there are hidden characters inside this string-value which can not be deleted).

Figure 7: Replace the thumbprint in the certificate dialog

Find an example for the thumbprint in the web.config which you have to replace below:

Figure 8: Token Signing thumbprint in the web.config.

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

How to enable debugging for DocumentsCorePack Server Based (ON PREMISE/IFD)

Wed, 27 Nov 2013 13:42:00 GMT

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

Please note: This article applies to

DocumentsCorePack ServerBased Document Generation & Processing
for Microsoft CRM 2013, 2015 and Microsoft CRM 2015/2016

ON PREMISE AND IFD ONLY

(Click here for information on debugging in DocumentsCorePack Online)

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

This article describes two different possibilities to activate debugging for DocumentsCorePack:

Solution 1: Activate debugging by using the AutoMerge Configuration (recommended)

Solution 2: Activate debugging manually via MSCRM-ADDONS.com Settingskeys

Furthermore, it provides you with information on how to access the logfiles.

Solution 1: How to enable debugging using the AutoMerge Configuration

Step 1

Open your CRM and navigate to Settings > Solutions.

Example for Microsoft Dynamics CRM 2015 and lower

Figure 1: Microsoft Dynamics CRM 2015 and lower

Example for Microsoft Dynamics CRM 2015/2016 and higher:

Figure 2: Microsoft Dynamics CRM 2015/2016 and higher

Step 2
With a double-click on the AutoMergeServerCore-solution...

Figure 3: All solutions > AutoMerge Core Solution

Open the AutoMerge configuration window:

Figure 4: AutoMerge Config

Step 3
Check Activate Debugging and Active File Debugging and click on the [Save]-button. Now debugging is activated.

Step 4

Please reproduce the error and enter the logfile.

Solution 2: How to enable debugging manually via mscrm-addons.com Settingskeys

Step 1

Navigate to Settings and select MSCRM-ADDONS.com Products.

Figure 5: Select MSCRM-ADDONS.com products

Step 2

In the next window, double-click on AutoMerge.

Figure 6: Active MSCRM-ADDONS.com Products

Step 3

This action will open the AutoMerge SettingsKey. Look for debugging and double-click on it.

Figure 7: AutoMerge debug

Step 4

This action will open the debug SettingsKey. Set the KeyValue on true (highlighted in yellow)
and click on the icon in the right corner at the bottom of the window (highlighted as well in yellow) in order to save your settings.

Figure 8: debug SettingsKey

Step 5

You will also have to activate the file-debugging. Therefore, click on filedebugging in the
AutoMerge Settingskey and apply Step 4 also to filedebugging.

Figure 9: filedebugging SettingsKey

Debug and filedebugging are now active. The log-files will be saved in the log-folder in your AutoMerge installation folder.

Please send the files in the log-folder with an error description to our support address (support@mscrm-addons.com).

How to access the logfiles

Navigate to the installation-path of AutoMerge and send the files in the log-folder with an error description to our support address (support@mscrm-addons.com).

Example how the path could look like:

C:\Program Files (x86)\PTM EDV-Systeme GmbH\AutoMerge for Microsoft CRM 2013\log

Figure 10: Example path I

Figure 11: Example path II

Figure 12: Example path III

Figure 13: Example path IV

How to activate local DCP service debugging

Please note: If you have a DocumentsCorePack service issue, please activate Debugging this way:

Go to the start-pane and look for the DocumentsCorePack ServiceManagement.
In the so opened window, you have the possibility to activate debugging, like you can see highlighted in yellow below.
Please note: The DocumentsCorePack service has to be stopped first.

Figure 14: Activate DCP service debugging

Once activated, proceed like above described.

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

Our addons’ compatibility with Dynamics CRM 2013, SharePoint, MS Office

Fri, 22 Nov 2013 12:27:00 GMT

In this article, you can find a compatibility chart for all our addons for Microsoft Dynamics CRM 2013.

It shows which of our addons are compatible with

· MS Dynamics CRM 2013 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
October 2013

Version

Last Version-Release Date

MS Dynamics CRM 2013

MS SharePoint

MS Office
(x86, x64)

On-Premise

Hosted
(IFD)

Online

Cross
Browser

2010

2013

online

2007

2010

2013

ActivityTools

6.7
and higher

11/11/2013

yes

AttachmentExtractor

2013.2
and higher

10/31/2013

yes

DocumentsCorePack

Server: 2013.31
and higher
Client: 6.5
and higher

11/11/2013
10/23/2013

yes

yes^*1)*2)

yes

GroupCalendar

6.5
and higher

10/21/2013

yes

PowerSearch

6.6
and higher

11/11/2013

yes

SmartBar

2013.5
and higher

01/29/2014

yes

TelephoneIntegration

Server: 6.3
and higher
Client: 6.3
and higher

10/23/2013
10/23/2013

yes

*1) At the moment, FileExplorer-documents, SharePoint-documents and the Document Summary are not compatible.
*2) All browser windows created by the application will open in the InternetExplorer.

Please do not hesitate to contact us via support@mscrm-addons.com 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.

Insecure content warning in IE when using FileExplorer with IFD

Mon, 17 Dec 2012 11:05:00 GMT

If you have configured your CRM for IFD and also have enabled our FileExplorer Integration, Internet Explorer (IE) will either not load the FileExplorer or show a message about insecure content.

Figure 1: FileExplorer not visible

Figure 2: Internet Explorer shows insecure content warning

If you run into this problem, please follow the steps below to resolve this issue.

There are two IE settings you need to modify

1. Add the DocumentsCorePack (DCP) Server FQDN DNS name to the trusted sites.
Open the IE Settings and on the Security-tab page, switch to Trusted Sites and click on Sites to add the fully domain name of DocumentsCorePack (e.g. https://documentscorepackserver.c3.ptm-edv.at)

Figure 3: IE Settings showing how to add DocumentsCorePack to the trusted sites

2. Modify the Local Intranet zone to allow mixed content
Open the IE Settings and on the Security-tab page, switch to Local Intranet and click on Custom Level to modify the settings.

Figure 4: IE Settings showing Local Intranet options

Then you have to scroll down to Miscellaneous and enable Display Mixed Content

Figure 5: Enable Display Mixed content

After you have applied these settings, please restart Internet Explorer.
Hereafter, the FileExplorer documents will be shown without any prompt in the an IFD environment.

Figure 6: FileExplorer Documents in IFD

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

Installing GroupCalendar and ActivityTools in an IFD/Claims-Based-Environment

Mon, 28 Nov 2011 20:09:00 GMT

This blog article will walk you through the required steps on how to install GroupCalendar and ActivityTools in a claims-based environment.

This article is valid for GroupCalendar for CRM 2011, 2013, 2015 and 2016 but only for CRM 2013 and older versions of ActivityTools. From CRM 2015 onwards ActivityTools does not have to be configured for IFD anymore!

The steps are the same for both products, so instead of an explicit product name, we will use the term the addon in this guide.

The IFD configuration for the GroupCalendar is as follows:

IFD-Tool -> Download Link you must have a login on our web site
For installing GroupCalendar you need at least version 5.12 from our Download Section
For installing ActivityTools you need at least version 5.13 from our Download Section

Before you start the installation, make sure that MS CRM is working correctly in IFD/Claims-Mode, including your ADFS, which should be installed correctly and configured to work with MS CRM.

More details on how to configure MSCRM for IFD/Claims can be found in the Microsoft Guide Configuring Claims-based Authentication for Microsoft Dynamics CRM 2011 Download

The following system configuration is the base for our guide.
Your setup will differ in these URLs, make sure you are replacing the URLs with your own URLs when following the guide.

Internal Url used to access Microsoft Dynamics CRM:
https://internalcrm.rc1ifd.ptm-edv.at

External Url used to access Microsoft Dynamics CRM:
https://[orgname].rc1ifd.ptm-edv.at

AD FS Server:
https://win2008domain.ptm-edv.at

The addon itself also requires a dns name:

https://activitytoolsserver.rc1ifd.ptm-edv.at (for ActivityTools)

https://groupcalendarserver.rc1ifd.ptm-edv.at (for GroupCalendar)

Basic installation/configuration of the addon:

Install the addon on the CRM Server.
You will be asked for the Logon Information. Fill in the internal IFD name of your CRM. In our case it is internalcrm.rc1ifd.ptm-edv.at
Now select the organization on which you want to install the addon and click on the [OK]-button.

Figure 1: Connection dialog
After the installation has finished, you have to open the IIS ( inetmgr.exe ) and go to Sites > the addon WebSite. Right click the ActivityToolsserver or GroupCalendarserver - WebSite and select Edit Bindings...

Figure 2: Select Edit Bindings...

On the Bindings, click on the [Add...]-button and select in the Add Site Binding the type https.
You also have to specify the port. In our example we use 4446

Figure 3: Add Bindings

With that we have made the website available for https. Now click on the [OK]-button.
Reselect the addon website and double click on the Authentication-item in the right side details pane.
Verify that the options Anonymous and ASP.Net Impersonation settings are enabled. ( Anonymous must be disabled with non IFD systems).
The addon URL must be added to your DNS Server.
Your DNS-Servers have to resolve the activitytoolsserver.[your-domain] or groupcalendarserver.[yourdomain] names correctly. That means, they should resolve it with the same IP-address your CRM Server has.
Please note: IF you are have an external DNS, make sure that both external and internal DNS are able to resolve the URL.
Extract the IFD-Tool (.zip-File), that you have downloaded before and execute the IFDSetupWizard.exe.
Follow the steps in the IFD Setup carefully.
Open your CRM in Internet Explorer and go to Settings > MSCRM-ADDONS.com Products > Open the addon. In the MSCRM-ADDONS.com Products form, select the MSCRM-ADDONS.com Settingskeys and search for the WebApplicationPort entry.

Figure 4: mscrm-addons.com Settingskeys
Open the WebApplicationPort and replace the existing KeyValue with the following:
[httpsPort]|[httpPort]|[claimsbased]|[addonname]|[debugging]

e.g.:
4446|5557|true|activitytoolsserver|false

We have finished the configuration of the CRM part and now need to configure the AD FS.

Please logon your AD FS Server and start AD FS 2.0 Management.
On the Actions menu located in the right column, click Add Relying Party Trust.
In the Add Relying Party Trust Wizard, click on the [Start]-button.
On the Select Data Source page, click on Import data about the relying party published online or on a local network, and then type in the URL to locate the federationmetadata.xml file.

This federation metadata is created with the IFD-Tool on the CRM Server. For example:
https://activitytoolsserver.rc1ifd.ptm-edv.at:4446/FederationMetadata/2007-06/FederationMetadata.xml

Type this URL in your browser and verify that no certificate-related warnings appear.
Click on the [Next]-button.
On the Specify Display Name page, type a display name, such as ActivityTools IFD, and click on the [Next]-button.
On the Choose Issuance Authorization Rules page, leave the Permit all users to access this relying party option selected, and then click on the [Next]-button.
On the Ready to Add Trust page, click on the [Next]-button, and then click on the [Close]-button.
If the Rules Editor appears, click on Add Rule. Otherwise, in the Relying Party Trusts list, right-click the relying party object that you created, click Edit Claims Rules, and then click on Add Rule.
Please note: Make sure the Issuance Transform Rules tab is selected.
In the Claim rule template list, select the Pass Through or Filter an Incoming Claim template, and then click on the [Next]-button.
Create the following rule:
• Claim rule name: Pass Through UPN (or something descriptive)

Add the following mapping:
i. Incoming claim type: UPN
ii. Pass through all claim values
Click on the [Finish]-button.
In the Rules Editor, click on Add Rule, and in the Claim rule template list, select the Pass Through or Filter an Incoming Claim template. Then click on the [Next]-button.
Create the following rule:
• Claim rule name: Pass Through Primary SID (or something descriptive)

• Add the following mapping:
i. Incoming claim type: Primary SID
ii. Pass through all claim values
Click on the [Finish]-button.
In the Rules Editor, click on Add Rule.
In the Claim rule template list, select the Transform an Incoming Claim template, and then click on the [Next]-button.
Create the following rule:
• Claim rule name: Transform Windows Account Name to Name (or something descriptive)

• Add the following mapping:
i. Incoming claim type: Windows account name
ii. Outgoing claim type: Name
iii. Pass through all claim values
Click on the [Finish]-button and when you have created all three rules, click the [OK]-button to close the Rules Editor.

You have finished the configuration and you should be able to use the addon in your IFD/Claims Environment now.

Troubleshooting:

Error message:

Figure 5: Error Message

Reason:

This indicates you are using a wrong certificate for the ADFS signing.

Solution:
Make sure the thumbprint in the web.config matches the one the token signing certificate in ADFS.

Error message:

Figure 6: Error Message

Reason:

This error could (also) indicate access rights problems with the certificates private key (mainly an issue for self signed certificates).

Solution:

Open your certificate store on the server (MMC, add certificate snapin for local computer) and find your HTTPS certificate. In the context menu, under all tasks select the manage private keys option and grant access to everyone.

Checklist for general troubleshooting:

Is the Setting WebApplicationPort still intact?
Are there any not http/https bindings in CRM?
Are there any not http/https bindings in the product website?
Is the DNS correctly resolving the products link?
Has the ConnectionProfile been created with IFD as connection type?

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

DocumentsCorePack IFD configuration

Thu, 18 Nov 2010 15:45:00 GMT

When using DocumentsCorePack (DCP) in different environments (office, home, etc.) it is necessary to configure 2 profiles for the client.

One for the IFD connection and one for the standard connection.
These profiles are configured via the DCP dataprovider on the client.

Please open the registry and add the the following string value to
Hkey_Current_User\Software\PTM EDV-Systeme\WordMailMergeClient.

String value= failoverprofile
Value for failover profile = GUID of the IFD profile.

Adding this setting to the current user will ensure that DCP switches between the profiles as soon as one of the connection types is not available.

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

How to configure DCP FileExplorer in an IFD Environment with WebDrive

Fri, 09 Jul 2010 12:17:00 GMT

In an IFD Environment it is hard to implement a FileShare which is available through the Internet. We found a product named WebDrive where you could configure, for example an FTP which will be mapped to a local drive.

Here is a link to the product website: http://www.southrivertech.com/products/webdrive/winindex.html

You are able to connect to FTP, WebDAV, FrontPage, GroupDrive, SFTP (ssh) and Amazon-S3.

We tested the tool and in combination with DCP FileExplorer Integration it works really fine.

To configure WebDrive, please follow the user guide of WebDrive. The important thing is, that you have to install WebDrive on the CRM Server and on all Clients. And the WebDrive must be mapped on all machines to the same local drive letter. E.g. W:\

Per default settings the WebDrive caches the files. So when one user creates a document and another user opens the file location, it could be possible that the file doesn’t exist for the second user because of the cache. In the WebDrive settings you have to set the Cache options to None.

Figure 1: WebDrive settings

After you have configured WebDrive to e.g. W:\ you have to configure the FileShare for the FileExplorer Documents in the DCP Config also to W:\

Figure 2: WebDrive settings - FileShare

Figure 3: DCP Server Config Setting

After these steps you should be able to use FileExplorer integration in an IFD environment.

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

CTI in a hosted environment

Fri, 09 Jul 2010 11:29:00 GMT

CTI does need the server component in a hosted environment as well, but you can launch the CTI Server setup from any Client, as long as you have a user with full access to CRM.

You need to select the hosted options on the Connection dialog.

If you have physical access to the CRM server, you can simply launch the setup on that server as if it were an onPremise installation.

Due to the mechanics of an IFD setup, the client will not use a SQL connection to retrieve the information, but a webservice call.

As webservice calls are more limited as SQL queries, it is recommended to create a hidden field in CRM on the entities you want to search in.

They will hold the numbers in a format similar to the one TAPI uses.

You can achieve this either via an onSave script or via a workflow in CRM, transmuting the number to a TAPI compatible format.

This is only required for caller identification, outbound calls will work with the formatted number, because they are processed by the Client application.

Explanation:

The number stored in CRM is formatted canonical, looking like +43 (316) 680880 0

The TAPI drivers delivers a number as 00433166808800.

Though the information is the same, the formatting prevents the CTI to find the number, as the webservice call is not able to resolve the formatting.

If you have a field in the CRM entity that is getting filled with the unformatted number, you can setup the CTI to use that field for the lookup and get correct results in looking up the callers, but still have a well formatted number in the CRM to display.

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