News.mscrm-addons.com Blog

How to delete metadata in DocumentsCorePack

Thu, 02 Mar 2017 12:26:12 GMT

This article outlines how to delete metadata in DocumentsCorePack.

Please note: It is important to close the DCP dataprovider and all open MS Word instances before you proceed.

Step 1: Open the metadata save location
To do so, please open the Windows Explorer and look for %appdata%\DCP\metadata. In this folder you will find a directory with your CRM organizations' name.

Figure 1: Look for metadata in the Windows Explorer

Step 2: Delete the metadata
Please delete all the files in that folder.

Figure 2: Delete metadata

Step 3: Restart MS Word and the DCP dataprovider
Last but not least, restart MS Word and the DCP dataprovider. Please learn how to restart the dataprovider here.

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

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 change the save location of the metadata.bin file

Wed, 30 Nov 2011 14:07:00 GMT

Per default, CRM metadata information for DocumenstCorePack is stored here:

%APPDATA%\DCP\metadata

The above location equals to C:\Users\[YourUsername]\AppData\Roaming\DCP\metadata.

If you want to change this location, you have to generate a new SettingsKey.

Click here to learn how to create a new SettingsKey.

The name of the key has to be "CommunicateToMSCRMFolderLocation" and as a value you must set a path, e.g. "c:\TEMP\" or "\\fileshare\TEMP"

Please note: This new key will affect all DocumenstCorePack Client installation! So you have to make sure that each DocumenstCorePack Client user has access to provided path!

Please note: The DocumentsCorePackDataProvider must be restarted on the Client afterwards!

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

Error message 401: Unauthorized when trying to access after deploying a custom web-application

Fri, 09 Apr 2010 11:45:00 GMT

The problem occurs because MS CRM is using an HttpModule for multitenancy scenarios. This http module is called with an anonymous user account. This is why it fails when trying to request, i.e. the metadata webservice.

Solution: To make it work, a new entry (remove CrmAuthentication) has to be specified within the web.config file of the specific Add-On.

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