News.mscrm-addons.com Blog

How to integrate SharePoint with CRM and MS Dynamics 365

Tue, 21 Mar 2017 16:28:49 GMT

This article outlines how to integrate SharePoint with CRM. It is valid for CRM 2013 and higher. This step-by-step tutorial shows you how to connect SharePoint with Microsoft Dynamics 365 and how to create SharePoint folders automatically.

Step 1: Please open the Document Management Settings. To do so, navigate to Settings > Document Management and click on Document Mangement Settings.

SharePoint path limitation avoidance

Tue, 21 Feb 2017 16:18:08 GMT

SharePoint paths limitations are hard coded. The maximum path length is 260 characters. If that limit is exceeded, you get the SharePoint error 414. This article outlines how to avoid this error.

Minimum requirements: AttachmentExtractor v.124 and/or DocumentsCorePack v.167 or higher

mscrm-addons products offer several default ways to shorten SharePoint paths:

1) We provide you with a default shortening to a maximum of 30 characters + GUID for each folder name.

2) We provide you with a default shortening to a maximum of 30 characters + GUID for each file name.
3) ShortIDs: We create a 6-characters ID alternatively to the well-known 36 GUIDs of Microsoft Dynamics 365 (CRM).
4) Use an alternative field for the generation of paths. (e.g. instead of account name we can use a unique account number field)

Please note: Even though the creation of short paths is a very valuable feature, existing paths cannot be shortened anymore, unless very specific criteria are met. Manual interaction is always required.

How to activate a ShortID for AttachmentExtractor

1) First, you must activate ShortID for AttachmentExtractor. To do so, please follow the below path in order to get to the ShortID settings.
Please note, that you must replace [YourServiceName] with your individual service name:

HKEY_LOCAL_MACHINE\SOFTWARE\PTM EDV-Systeme\AttachmentExtractorserver\Configurations\[YourServiceName]

2) Next, set UseShortID to true.

3) To define the cutting, you will have to create a new settingskey. If you have not created a settingskey yet, please have a look at this article.

Depending on which item you would like to customize, please enter the following settings:

For the maximum SharePoint folder name length:
SPMaxFolderLength: [number of characters that should remain]

For the maximum SharePoint file name length:
SPMaxFileLength: [number of characters that should remain]

For the minimum SharePoint file name length:

SPMinFileLength: [minimum number of characters that should remain]
Please note: The file extension is never cut!

Let us pretend, the minimum filename length set is 77.

If the actual file length is, for example, 80, you will receive an error message.

For the SharePoint folder name attribute:

SPFolderNameAttribute: enittyschemaname;attributename|

How to activate a ShortID for DocumentsCorePack

Creating a ShortID for DocumentsCorePack is easier than creating one for AttachmentExtractor. Simply navigate to Settings > DocumentsCorePack in your Microsoft Dynamics 365 (CRM) application.

Here, please add/enable the following options:

Use short Documentation Logic:
This setting cuts SharePoint path automatically.

SharePoint folder maximum length:
This setting cuts SharePoint folder names that are longer than a certain amount of characters.

For further information on how to correct SharePoint paths exceeding the limitations, please have a look at this blog article.

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

AttachmentExtractor SharePoint attributes

Wed, 01 Feb 2017 16:36:08 GMT

SharePoint attributes deliver additional information on the file origin based on CRM metadata. This article outlines the purpose of the different attributes.

Figure 1: SharePoint attributes

❶ Backlink to Microsoft Dynamics 365 (CRM)
This attribute backlinks to the original item in CRM from which the attachment (email or note) has been extracted previously.

❷ Entity GUID (note/email)
means the unique type GUID of the entity's origin.

❸ Entity type (note/email)
means the unique type name of the entity's origin.

The CSV lists mentioned in point 4 & 5 generally refer to metadata (GUID or text) in Microsoft Dynamics 365 (CRM).
Emails and annotations consist of both, GUID-, as well as text-fields.

❹ CSV GUID-list containing metadata regarding the recipient/owner
For EMAILS, the CSV GUID list contains the following attributes:

from

bcc
(subject*)

regardingobjectid

The list contains a list of EntityReferences to CRM records. This applies to the fields from, to, cc, bcc, regardingobjectid. *The field 'subject' is a text field.

If a field contains multiple values, those values are separated by a pipe symbol:

Example for EMAIL (please note the empty entry for bcc):

sender@mail.com;recipient1@mail.com|recipient2@mail.com;
ccrecipient@mail.com;;myemailsubject;regardingaccountname

{599FC5EE-345E-4505-9467-2F05B90E0A15}|contact;{57561E8A-E8D6-43B3-A212-BF9C173F56BF}|systemuser|
{7F9CB1CF-84B9-4B7F-A036-78F3388ED5D7}|systemuser;{E5B66E6C-02F8-4DD8-98E9-D06E4A46965A}|
systemuser;;;{157E2666-6EA2-41E2-9E32-31F17BB1EE7C}|account

❺ CSV text-list containing metadata regarding the recipient/owner
For NOTES, the CSV TEXT list contains the following attributes:

Subject
Filename
Filesize
Notetext
(objectid*)

The CSV Text list contains a list of references to annotations. This applies to the fields subject, filename, filesize, notetext. *The field 'objectid' is a GUID-field.

Example for a NOTE (please note the empty entry for notetext and Object ID):

subject;filename;filesize;;;

02_Quote; 02_Quote.pdf; 15447;;;

❻ Record type
This attribute provides you with information regarding the CRM record type.
Set on 'Yes', this attribute refers to an email or note body, set on 'No', it refers to an attachment.

❼ Entity date
Contains the entity's creation date.

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

For ANNOTATIONS, the CSV GUID list contains the following attributes:
ObjectID

How to correct SharePoint paths exceeding the limitations (Advanced)

Tue, 31 Jan 2017 12:33:00 GMT

This article provides you with information on how to correct SharePoint paths exceeding the limitations. Please note, that this article is only considered to serve advanced Microsoft Dynamics users and only if you have received the SharePoint error 414 previously. The information provided here is connected to the SharePoint path limitation avoidance article, which can be found here.

How do I correct potentially exceeding paths?

Please check the existing library structure. This is required for EVERY record separately.
Please note: The path logic should be modified before fixing existing problems, as CRM might recreate the folder applying the old path logic again.

Scenario 1) The SharePoint library is empty (no files AND no folders)

a) Delete the SharePoint library

b) Next, please delete the document location in CRM

When the library is created anew, the updated path logic will apply.

Scenario 2) The SharePoint library contains items (files or folders)

Please note: Renaming any folders in SharePoint will break the AttachmentExtractor URL in CRM that points to those records. This makes the attachments inaccessible from within CRM!

a) Rename the SharePoint folder
Please note: You can only rename folders!

b) Update the document location in CRM

Please make sure, that the created path matches the nomenclature of the folder definition in your CRM. Otherwise, new folders will be generated, rendering the folder name change useless.

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

SharePoint Documents Button Error – SmartBar

Fri, 15 Jan 2016 14:29:00 GMT

Sharepoint Documents Button Error – SmartBar

If you encounter an error, after -clicking- on the Documents Button inside SmartBar 2015/16 please follow this blog article.

SmartBar is per standard using the Client-based SharePoint integration view. If you instead use the Server-based integration on your CRM System, your click could result in one of the following errors:

Internet Explorer (frame error)

Figure 1: IE Frame error

Chrome (blank)

Figure 2: Chrome (blank)

Solution

Please Navigate to Settings -> MSCRM-ADDONS.com Products -> SmartBar and create a new SettingsKey. Check this Blog Article if you don’t know how to create one.
Fill in the following values and click on save:

Name: UseServerBasedSP
IsCached: Yes
KeyValue: true

Figure 3: New MSCRM-ADDONS.com Settingskeys

After clicking on the SmartBar Documents Button now, you should see the correct view without any errors.

Figure 4: Correct view without errors

That's it! We appreciate your feedback on our products and blog! Please share your thoughts by sending an email to support@mscrm-addons.com!

Sharepoint Metadata (Dynamics 365)

Mon, 23 Nov 2015 13:47:00 GMT

The latest version of DocumentsCorePack Server Based supports the population of metadata into SharePoint. Proper configuration of Dynamics 365 and DocumentsCorePack for the Dynamics 365 Integrate SharePoint is needed as well.

Please note: Only base types are supported, taxanomy properties are currently not supported.

The below screenshot shows a property that was created by DocumentsCorePack
with data from Dynamics 365 (1).

Figure 1: Example of SharePoint Metadata
If you are not sure how to access the template settings to set the
SharePoint metadata, please have a look at this article first.

Access the SharePoint Metadata section

Figure 2: SharePoint Metadata section
Add, edit or delete a property
- To add a property use the [Add]-button (1)
- To edit a property select an element (4) and hit the [Edit]-button (2)
- To delete a property select an element (4) and hit the [Delete]-button (3)

Figure 3: Add/Edit/Delete a property
Create a new property
After you have selected Add/Edit the SharePoint Metadata Field Settings
a window will pop up.
You have to manually type the name of the SharePoint property. (1)
How to create, change or delete custom properties on the Sharepoint is
described in this external blog by Microsoft.
The value of the property can be composed of Dynamics 365 fields and fixed text.
More details about the supported syntax for this field can be found here.

Figure 4: SharePoint Metadata
Save your template
Before you can use or test your template you have to save it. Either you save your template locally with the standard Save or Save as the functionality of Word or you use the Save template-option of the DocumentsCorePack client in order to publish the template to Dynamics 365.
Test your template [optional]
As you have made changes to your template you might want to test it quickly. A step by step description of how to test your template can be found here.

Related topics:
List of available template settings

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

How to create SharePoint locations, folders and subfolders automatically in DCP SB Online?

Thu, 30 Apr 2015 10:12:00 GMT

This blog article outlines how to create SharePoint locations, folders and subfolders automatically within MS Dynamics CRM with our DocumentsCorePack ServerBased Add-On.

The solution is our AutoMergeWorkingItem which can be triggered automatically when creating a new workflow in a process.

Requriement: DocumentsCorePack ServerBased (DCP SB) Online

For further information how to do this in DCP OnPremise, please click here.

Example:

Standard SharePoint location in CRM:

Figure 1: Standard CRM SharePoint window

Created SharePoint location:

Figure 2: Created SharePoint location

How to manually save SharePoint locations, folder(s) and subfolder(s) in CRM when creating an account

Generally, when creating a new account in MS CRM, all appropriate documents (e.g. quotes, invoices etc.) are saved in the entity Documents in MS CRM.
As you can see in Figure 3, the CRM Save location Documents can be accessed via the drop-down-button next to the current company in the main navigation area at the top.
It could as well be accessed using our addon SmartBar, which enables a simple navigation between all related CRM records and entities.

Figure 3: Save location of documents in MS Dynamics CRM

Anyway, to create a new Account in CRM, navigate to Accounts, then click on the [New]-button.

Figure 4: Create a new account in MS CRM.

When you click on Documents (see Figure 3), the following message box appears. The box indicates, that a SharePoint location will be created manually with a click on the [OK]-button.

Figure 5: Message from webpage

The standard SharePoint location-window is empty and does not contain any folder(s) or subfolder(s).

Figure 6: Entity Documents, once an account has been created.

Once documents have been saved, its look changes.

Figure 7: Entity Documents with saved content

How to create a workflow that automatically generates SharePoint locations, folder(s) and subfolder(s) when creating an account

It is possible to create different subfolders in folders that contain certain documents (e.g. Quotes, Invoices …)

This can be managed with a simple workflow.

In our example we define

1) the SharePoint location,
2) the folder(s) and
3) the subfolder(s)
that will be automatically triggered when creating a new account.

First of all, open your CRM and navigate to Settings and Processes.

Figure 8: CRM > Settings > Processes

Now create a new process with a click on the [New]-button.

Figure 9: Create a new process

In the next window, define the following settings:

- Process Name: (here: CreateSharePointFolder)
- Activate As: Process
- Entity: (here: Account)
- Category: Worfklow

Once this is done, click on the [Add Step]-button and select Create Record.

Figure 10: Add a new step (Create record)

Now name the step (here: CreateFolder) and open the Drop-down menu within this first step:

Figure 11: Name the new step

There, select MSCRM-ADDONS.com AutoMergeWorkingItems.

Figure 12: AutoMergeWorkingItems

Next, click on the [Set Properties]-button.

Figure 13: Set properties for the new step

In the now following window, type in a name and define the AutoMergeWorkingItem-action (here, CreateSharePointFolder) It is also important to insert the PrimaryRecordUrl. To do so, set the cursor into the PrimaryRecordUrl-field and go to the Look for: -area within the form assistant on the right side. There, select Records URL(Dynamics) form the second drop-down menu. Click on the [Add]-button and on the [OK]-button in order to proceed.

Figure 14: Create MSCRM-ADDONS.com AutoMergeWorkingItems

Next scroll down to the Create SharePoint Folder-section (see next screenshot, click to enlarge)

Figure 15: Create SharePointFolder-section

There, you can define the SharePoint location, folder(s) and subfolder(s).

For example: TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 16: Example SharePoint subfolder added

Figure 17: Structure of TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 17 outlines, that a slash indicates that the subfolder remains in a mainfolder. Furthermore, it outlines that a semicolon indicates the creation of a new main folder.
Please note: the folder and/or subfolder name can contain blank space but you must not use a blank space between a folder and its subfoler(s)

Once you have set up your order structure, please click on the [Save and Close]-button.

Now click on the [Activate]-button in order to activate your workflow:

Figure 18: Activate workflow

Then click once again on the [Activate]-button in order to confirm the process:

Figure 19: Confirm the process

Now, your workflow is activated.

Figure 20: Activated workflow

Please note: it can take some minutes until the workflow has been entirely finished!

When you now create a new account and then navigate to the SharePoint document location, it should look similar to the example in Figure 21.

Figure 21: Example - SharePoint document location based on workflow

When opening the TEST-folder, the subfolders look as shown in Figure 22 and Figure 23.

Figure 22: Subfolder I

Figure 23: Subfolder II

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

SharePoint ErrorMessage: No part of the path in DCP SB Online

Tue, 14 Apr 2015 13:28:00 GMT

This blog article explains what to do when you receive the following error message while saving documents to SharePoint.

DocumentsCorePack failed to generate the document

Addon: DocumentsCorePack ServerBased (Online)

Please find here the OnPremise version of this blog-post.

Please note: The error usually occurrs because of missing or false SharePoint user credentials/rights.

It is mandatory that you have administrative access to SharePoint if you want to correct this error.

1) Go to www.mscrm-addons.com and log in with your credentials

Figure 1: www.mscrm-addons.com login

2) Next go to My Account and click on My cloud services

Figure 2: My Account > My Cloud Services

3) The DocumentsCorePack Online Configuration appears. Please mark the service and click on the [Configure Service]-button.

Figure 3: Open the service configuration

4) Please check if username and password are correct, as well as if the user has administrative access to the configured SharePoint.

Figure 4: Check your credentials

5) If everything is alright, click on the [Save Service]-button and try it again!

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

SharePoint ErrorMessage: No part of the path in DCP SB (OnPremise)

Tue, 14 Apr 2015 12:44:00 GMT

This blog article outlines what to do if you receive the following error message while saving documents to SharePoint.

DocumentsCorePack failed to generate the document

Addon: DocumentsCorePack ServerBased CRM 2013/2015 (OnPremise)
Please find here the Online version of this blog-post.

Please note: The error usually occurs because of missing or false SharePoint user credentials/rights.

It is mandatory that you have administrative access to SharePoint if you want to correct this error.

Minimum permission of SharePoint user:
Able to logon to the root site of SharePoint
Read access on the site
Read and write on the document library and all subfolders (create folders and upload files)

For impersonation and SharePoint attributes: Site admin rights

1) Open your Dynamics 365 and navigate to Settings

Figure 1: Dynamics 365 - Settings

2) In the Settings, click on Solutions

Figure 2: Solutions

3) There, double-click the DocumetsCorePackServerCore Solution.

Figure 3: DocumetsCorePackServerCore Solution

4) Please enter the credentials for your SPS user, the SPS password and the SPS domain.

Figure 4: Enter the credentials for the SPS user, password and domain

5) Now click on the [Save]-button and try again.

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

How to create SharePoint locations, folders and subfolders automatically in DCP SB (OnPremise)?

Wed, 18 Mar 2015 13:00:00 GMT

This blog article outlines how to create SharePoint locations, folders and subfolders automatically within MS Dynamics CRM with DocumentsCorePack ServerBased, using a simple workflow.

Add-On: DocumentsCorePack ServerBased (OnPremise)

For the MS Dyn CRM Online version of this article, please click here.

Example:

Standard SharePoint location in CRM:

Figure 1: Standard CRM SharePoint window

Created SharePoint location:

Figure 2: Created SharePoint location

Figure 3: Save location of documents in MS Dynamics CRM

Anyway, to create a new Account in CRM, navigate to Accounts, then click on the [New]-button.

Figure 4: Create a new account in MS CRM.

When you click on Documents (see Figure 3), the following message box appears. The box indicates, that a SharePoint location will be created manually with a click on the [OK]-button.

Figure 5: Message from webpage

The standard SharePoint location-window is empty and does not contain any folder(s) or subfolder(s).

Figure 6: Entity Documents, once an account has been created.

Once documents have been saved, its look changes.

Figure 7: Entity Documents with saved content

How to create a workflow that automatically generates SharePoint locations, folder(s) and subfolder(s) when creating an account

It is possible to create different subfolders in folders that contain certain documents (e.g. Quotes, Invoices …)

This can be managed with a simple workflow.

In our example we define

1) the SharePoint location,
2) the folder(s) and
3) the subfolder(s)
that will be automatically triggered when creating a new account.

First of all, open your CRM and navigate to Settings and Processes.

Figure 8: CRM > Settings > Processes

Now create a new process with a click on the [New]-button.

Figure 9: Create a new process

In the next window, define the following settings:

- Process Name: (here: CreateFolder)
- Activate As: Process
- Entity: (here: Account)
- Category: Worfklow

Once this is done, click on the [Add Step]-button, select AutoMergeWF and CreateSharePointFolder.

Figure 10: Add a new step (CreateSharePointFolder)

Now name the step (here: CreateFolder) and click on the [SetProperties]-button:

Figure 11: Name the new step

In the following window, define the SharePoint location, folder(s) and subfolder(s).
For example: TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 12: Example SharePoint subfolder added

Figure 13: Structure of TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 13 outlines, that a slash indicates that the subfolder remains in a mainfolder. Furthermore, it outlines that a semicolon indicates the creation of a new main folder.
Please note: the folder and/or subfolder name can contain blank space but you must not use a blank space between a folder and its subfoler(s)

Once you have set up your order structure, please click on the [Save and Close]-button (see Figure 12).

Now click on the [Activate]-button in order to activate your workflow:

Figure 14: Activate workflow

Then click once again on the [Activate]-button in order to confirm the process:

Figure 15: Confirm the process

Now your workflow is activated.

Figure 16: Activated workflow

Please note: it can take some minutes until the workflow has been entirely finished!

When you now create a new account and then navigate to the SharePoint document location, it should look similar to the example in Figure 17<.

Figure 17: Example - SharePoint document location based on workflow

When opening the TEST-folder, the subfolders look as shown in Figure 18 and Figure 19.

Figure 18: Subfolder I

Figure 19: Subfolder II

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.

The request failed with HTTP status 401: Unauthorized

Thu, 03 Apr 2014 12:04:00 GMT

This article outlines what to do if you get the following failure notice: Request failed wiht HTTP status 401: Unauthorized.

Requirements: WordMailMerge

Example:

Figure 1: WordMailMerge Error The request failed with HTTP status 401: Unauthorized.

Also this error message could occur.

Figure 2: Alternative error message

If you click on the [Create Document]-button, you should get the following error message:

Figure 3: Another related error message

Why do you receive these error messages?
If you are in a Windows Server 2003 functional level domain and the CRM and SharePoint are installed on different servers, you get this error because Windows default security does not allow delegation. This means, that the CRM server is not allowed to forward the user credentials to SharePoint and so, the SharePoint login failes for all anonymous users.

Workaround
At the moment, there is only a workaround to overcome this problem. You could select one special user for this. All document and template related connections will be processed via this user and so you have no control about template-security. All WordMailMerge users have the same permissions as the user you select for impersonation. To set this user, open the WordMailMerge web.config in the installation directory (C:\Program Files\PTM EDV-Systeme GmbH\WordMailMerge Server for MS CRM 3\web.config) and add the following line in the system.web-node: .

Figure 4: workaround

Another Possible Solution
There is another solution with full functionality. But if you want to apply this solution, you definitely need some knowledge about your network infrastructure and security. Please read the article to end before you change anything!
At the moment it is only tested with SharePoint Server 2007 and SharePoint Services 3.0.

Configuration on Domaincontroller
Open Active Directory Users and Computers on the domain controller and find your CRM Server. Open the properties and go to the Delegation-tab. Change the setting to Trust this computer for delegation to any services (Kerberos only).

Figure 5: Configuration on Domaincontroller

Configuration on CRM Server
You must change the authentication provider to Kerberos. To do so, simply follow the Knowledge-Base article from Microsoft.

A short explanation of this step:
1. Open the ISS Manager and find out the Website-ID of the CRM application. See next screenshot:

Figure 6: IIS Manager

2. Click on Start, Run ..., enter cmd and click on Enter. Change to C:\inetpub\adminscripts. Enter the following line:
cscript adsutil.vbs set w3svc/##/root/NTAuthenticationProviders Negotiate,NTLM
(## stands for the ID you found out in the previous step)

Configuration on SharePoint
First you have to change the IIS Applicationpool User. Please make sure that the NetworkService has enough rights for the SharePoint-database! To change this, open IIS Manager and open the properties of the SharePoint Application Pool. Switch to the Identity-tab page and change the Predefined user to Network Service.

Figure 7: SharePoint - Properties

Now you can change the SharePoint itself to Kerberos. To do sp, open Start > Administrative Tools > SharePoint 3.0 Central Administration. Go to the Application Management-tab and click on Authentication Providers.

Figure 8: Application management window

Please change the Integrated Windows authentication to Negotiate (Kerberos)

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

Use DocumentsCorePack with CRM 2011 list components for SharePoint

Tue, 18 Jun 2013 11:13:00 GMT

This article is only relevant if you are using SharePoint folders or SharePoint sites integration of DocumentsCorePack. It does not concern DocumentsCorePack in combination with the CRM integrated SharePoint.

It describes how to use MS CRM 2011 list components to show and manage SharePoint documents of your DCP folder or site configuration.
It is available from DCP Server version 5.43 on and works with SharePoint 2010 and 2013.

How to activate it

First, you have to install the MS CRM list components for SharePoint. The installer can be downloaded by using this Link.

Next, create a new product setting for DocumentsCorePack.

Name: SPSUseCRMListComponents

IsCached: Yes

Value: true

This article explains how this can be done.

To test whether MS list components were enabled successfully or not, close all InternetExplorer instances, reopen them and click on SharePoint Documents.

The result should look like the following:

Figure 1: SharePoint Documents

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

AttachmentExtractor: How to customize entity folders and attributes in Sharepoint

Tue, 11 Jun 2013 12:10:00 GMT

This feature requires AttachmentExtractor 5.24 or higher.

Outline

1.) It enables AttachmentExtractor to create custom folder structures based on entity data from the regarding (email) or parent entity (annotation).

2.) It enables AttachmentExtractor to create custom attributes on the SharePoint and fill them with data from regarding (email) or parent entity (annotation).

HowTo

The customization is requiring two new settings in the registry.

Create you configuration in the servicemanagement as usual and save it. Open the registry editor and find the configuration node:

HKEY_LOCAL_MACHINE\SOFTWARE\PTM EDV-Systeme\AttachmentExtractorserver\Configurations

Find the Key, that is named identically to the configurationname you have selected, eg. crmonline

You need to create two new string setting in that branch:

CustomConfiguredEntitiesAsCSV

and

CustomMetaDataMappingAsCSV

Data structure for CustomConfiguredEntitiesAsCSV

The configured entities are a list, separated with semicolons and following this schema :

entity_schema_name|attribute.attribute.attribute

entity_schema_name is the unique name of the entity, that would trigger a custom path, when a regarding (email) or parent (annotation) entity of the specified type is being identified.

The "." separated value list is a list of the attributes, that should be evaluated for path generation. Supported field types are entityreference, optionsets and value fields (Text or number)

Example

account|createdby.name.territorycode;new_policy|new_policyholder.new_policyyear.new_policytype

The above setting will create a folder path with createby name , account name and territorycode optioenset value.

myusername/mycustomername/territorycodeoption1

Custom entities are supported.

Data structure for CustomMetaDataMappingAsCSV

The configured entities are a semicolon seperated list following this schema:

attributename|attributefield;attributename|attributefield;

Example

HGCName|name;HGCAttrib1|territorycode;HGCCustomer|customerid

AttachmentExtractor will create a new attribute and try to identify a field on the regarding (email) or parent (annotation) entity, which is named as defined and copy the content of that field into the attribute on the sharepoint. Supported field types are entityreference, optionsets and value fields (Text or number)

Custom fields are supported.

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 the DCP UploadFile SharePoint webservice

Wed, 15 May 2013 17:02:00 GMT

1. Open the IIS on the SharePoint server and navigate to the SharePoint Site where DocumentsCorePack (DCP) is configured and the UploadFile.asmx WebService is installed. Select the IIS Website and click on Explore as marked in Figure 1.

Figure 1: Click on explore

2. This brings up an explorer window. There you’ll find a web.config. Please open that file.

Figure 2: Open explorer window

3. Please add to the appSettings-section.

Figure 3: Add

4. After the error is reproduced, you’ll find the debug.log in that directory.

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

DocumentsCorePack - Configuration Chart

Wed, 08 May 2013 12:56:00 GMT

The below chart provides you with an overview of the possible configuration scenarios of CRM and SharePoint
together with DocumentsCorePack and AutoMerge for CRM 2011

This chart applies to DocumentsCorePack client versions 5.84 or higher,
DocumentsCorePack server version 5.41 or higher and AutoMerge versions 5.32 and higher.

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

Issues with the automatic generation of folder locations in CRM Online and SharePoint Online

Wed, 08 May 2013 10:15:00 GMT

If you you experience issues with the automatic generation of SharePoint Online folder locations for the CRM integrated SharePoint solution,
this article provides you with a solution. (For both, DocumentsCorePack and AutoMerge, the steps are the same.)

Please note: These steps are only necessary, if you have performed an upgrade of DocumentsCorePack or AutoMerge previously
and now, the automatic folder creation does not work for one of these add-ons any longer for CRM SharePoint Online.

Please note: At least version 5.84 of DocumentsCorePack Client, or version 5.32 of AutoMerge has to be installed!

1) Modify the following SettingsKey for the specific product manually and set its value to no.
If it does not exist please try to create it.

Name: SPWebserviceUrl

Value: no

Figure 1: Modify Settingskey

How to create a SettingsKey manually is described here (Steps 1-4).

If you create a SettingsKey for DocumentsCorePack please restart the DocumentsCorePack datatprovider afterwards!
Otherwise the change will not take effect!

If you experience the problem with AutoMerge, please make sure that you have entered a SPS User and the
SPS password in the AutoMerge Config. The AutoMerge Config opens if you open the MSCRM-ADDONS.com AutoMerge Server Core-solution.

Figure 2: SPS user and SPS password

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

The compatibility of our addons with Dynamics CRM, RU12, SharePoint and MS Office

Thu, 24 Jan 2013 10:08:00 GMT

In this article, you can find a compatibility chart for all our addons. It shows which of our addons are compatible with

· MS Dynamics CRM 2011 On-Premise/Hosted (IFD)/Online

· RollUp 12

· MS Sharepoint 2010/2013/Online

· MS Office (x86, x64) 2007/2010/2013

· and which of them support cross-browsing.

This is very useful if you want to know a priori if our addons are compatible with other software you are using or if you will be confronted with interface problems.

Please note: We update our addons constantly.

Last Update
5/14/2013

Version

Last Version-Release Date

MS Dynamics CRM 2011

MS Sharepoint

MS Office (x86, x64)

On-Premise

Hosted
(IFD)

Online

RU12

Cross
Browser

2010

2013

online

2007

2010

2013

ActivityTools

5.33
and higher

02/01/2013

yes

yes^*3)

yes

AttachmentExtractor

5.16
and higher

12/14/2012

yes

AutoMerge

5.24
and higher

12/27/2012

yes

DocumentsCorePack

Server: 5.39
Client: 5.76

03/21/2013
02/21/2013

yes

yes^*1)*2)

yes

GroupCalendar

5.47
and higher

03/04/2013

yes

PowerSearch

5.33
and higher

09/19/2012

yes

RecordCounter

5.18
and higher

01/29/2013

yes

TelephoneIntegration

Server: 5.32
and higher
Client: 5.52
and higher

02/01/2013
02/27/2013

yes

yes^*2)

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.

*3) Limited functionality as described on the ActivityTools product page.

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

Execute AutoMerge for MS CRM 2011 and 2013 via JavaScript

Fri, 19 Oct 2012 11:32:00 GMT

This article explains how to execute the Create Document-step of AutoMerge manually in JavaScript. This allows to include this functionality in custom - applications (e.g. create documents via a CRM-button-click and save document to SharePoint )

This article covers both:

1) Calling the plugin

2) Handling the result

Attached, you can find the full library for download.

How to start the Create-Process

The Create Document-part of AutoMerge is installed as plugin in CRM. To trigger this plugin, you have to execute a Retrieve Multiple-request on the MSCRM-ADDONS.com AMTrigger (logical name: ptm_mscrmaddonscomamtrigger)-entity. It is important that the result-attributes-list contains the ptm_FullXML-attribute. It will contain information returned by the plugin.
In addition, the request must include two filter conditions.
The first condition needs to ensure that solely the record with the name cmd_automerge will be returned.
The second one is a pseudo-condition which is used to pass information to the plugin. This information has to be in XML-format and has to look like this:

   false
   Create
   069E5412-84F6-E111-977B-00155DC8AE09
   account
   00BDBD7D-65DD-E111-BEC0-00155DC8AE09
   docx
   1

Description of parameter
•    EnableSingleDebugging: Here you can define if this step should be debugged. Options: true, or false. It is recommended to always define it as false. If debugging is needed, activate it via the AutoMerge configuration.
•    MessageType: Must be Create
•    PrimaryEntityId: The Id of the record for which the merge process should be executed.
•    PrimaryEntityLogicalName: The logical name of the starting entity.
•    TemplateId: The Id of the template which should be used for the merge process.
•    SaveAs: Defines the file format of the generated document (docx, doc, pdf,…).
•    SaveLocation: There are two options. 0: the document will be saved only in the MSCRM-ADDONS.com User/Temp Settings-entity. 1: the document will be saved in the MSCRM-ADDONS.com User/Temp Settings-entity and in File Share or SharePoint (depending on your setup of the DocumentsCorePack server configuration).
•    PrintTo: If the generated document should be printed as well, define the path of the network printer here.

Example
The Retrieve Multiple-request looks like the following:

var filter = "";
filter += "false";
filter += "Create";
filter += " 069E5412-84F6-E111-977B-00155DC8AE09 ";
filter += " account ";
filter += "00BDBD7D-65DD-E111-BEC0-00155DC8AE09";
filter += "docx";
filter += "1";
filter += " ";
filter += "";

$ptm.retrieveMultiple("ptm_mscrmaddonscomamtriggerSet", "?$filter=(ptm_name eq 'cmd_automerge') or (ptm_FullXML eq '" + filter + "')&$select=ptm_FullXML", CreateDocumentFinished, CreateDocumentError);

CreateDoucmentFinished and CreateDocumentError specify the CallBack-function after executing the request.

Process the results

After the request is executed, you will receive a result from the plugin.

Successful result
A successful result message looks like the following:
„AM_6_17<>valid|533d31c2-72da-e311-a232-00155dc80d02|outgoingBytes:63510|”
•    “AM_” is static text
•    “6_17” is the plugin version
•    “<>valid” is static text
•    “533d31c2-72da-e311-a232-00155dc80d02” is the ID of the generated “MSCRM-ADDONS.com User/Temp Settings”-record. It contains the generated document in the “Notes”-section. If the document is stored in SharePoint or File share, you can find the full path to the document in the “Value”-attribute.

Unsuccessful result
An unsuccessful result message looks like this:
“ERROR:|CHECKLICENSE|SUCCEEDED|new AutoMerge|StartMerge|EmptyGUID||ErrorMerge|BeforeCreateDoc
AfterCreateDoc”

or like this:
"AM_13<>validERROR"

Example
Below you can find a function which handles the result. If the process was successful, the documentId will contain the Id of the created MSCRM-ADDONS.com User/Temp Settings-record. If not, an error message will be shown.

Created MSCRM-ADDONS.com User/Temp Settings-record:

Figure 1: MSCRM-ADDONS.com User/Temp Settings

1: ID retrieved from the plugin. This ID references the mscrm-addons-temp record with the doucment attached
2: Link to the document on SharePoint: needed if you want to e.g. open the doucment from SharePoint
3: Attached document: Needed to process the temp-document

JavaScript-Example

Attached you can find the whole JavaScript-example. It uses the ptm_GeneralJSFunctions.js and ptm_jquery1.4.1.min web resources to trigger the plugin. They were imported during the installation of DocumentsCorePack server.
If you do not want to use this library, of course you can trigger the plugin with a standard HTTP request.

TriggerAM-Plugin.zip (1.29 kb)

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

CRM entities created during the installation

Wed, 18 Jul 2012 16:18:00 GMT

Each product installs the following entities in CRM:

ptm_mscrmaddonstemp

Containing pre-user & temporary settings

ptm_mscrmaddons_settings

Container for ProductSpecific settings

ptm_mscrmaddonscommetadata

Containing metadata of CRM for products

ptm_mscrmaddons_key

Sepcific Key/value pairs for product settings

ptm_mscrmaddonscom_debug

Entity storing debug information for actions where no file access is allowed.

Also, each product installs a new Security Role, mscrm-addons general security role.
This security role is covering the required access rights for the entities listed above.

Product specific entites for DocumentsCorePack (DCP):

ptm_dcpspssiteconfig2011

Saves information about Sharepoint Storage of documents

ptm_mscrmaddons_dcptemplates

Contains the DCP Templates required for creating the documents.

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