How to Replace PowerAttachment with a Power Automate Flow

With PowerAttachment, users were able to set attachments to automatically sync to their SharePoint sites – stripping the actual attachment from Dynamics 365 and replacing it with a link to the document that is now stored in SharePoint. It works with all entities and their attachments. And if you ever needed to leave attachments intact for a specific entity, you could simply define the entity in the PowerAttachment configuration, and the solution would ignore those attachments. It was a slick PowerObjects-designed solution that we deprecated on June 30, 2020.

Why would we sunset such a useful tool? A simple flow built using Microsoft technology essentially renders PowerAttachment obsolete. We can still fight the Dynamics 365 storage war – we’ll just do it with the help of Power Automate!

Power Automate gives end users the ability to automate tasks for themselves. It’s true! As the name suggests, Microsoft Power Automate is all about process automation. It allows anyone with knowledge of the business process to create repeatable flows that when triggered leap into action and perform a process for them. In this post, we’ll show you how to use Power Automate to replicate the PowerAttachment functionality. You will learn how to:

Let’s get started!

Power Automate flow for moving attachments from D365 to SharePoint

1. Go to https://flow.microsoft.com/ and sign in for a trial version of Power Automate (or subscribe).

2. After you log in to Power Automate, Click MyFlows from the left navigation pane.

3. Click New > Automated–from blank.

4. Give a suitable name to your flow in the Flow name field and also choose the trigger for your flow . For this example, select When a Record is created.

5. Provide the details (as described below) and click + New step

6. Search ‘SharePoint create a file’ under All and click Create file.

7. Fill in the required details and click + New step.

8. Search ‘SharePoint create sharing link’ under All and select Create sharing link for a file or folder.

9. Fill in the details as show below and click + New step.

10. Search for and select Update a record.

11. Fill in details as shown below and click Save.

Now your Power Automate flow is ready. Go ahead and create a note in any entity and add an attachment to it. Refresh the page and see the attachment is replaced with a SharePoint link.

Before:

After:

You can also use create some advanced features like moving only PNG files or moving attachments only from an Accounts entity, or if you wish to keep attachments in a single folder.

Advanced Features:

Scenario 1: If you want to move only PNG file types to SharePoint.

1. Under When a record is created, click Add an action.

2. Search for and select that Condition control.

3. Mention the condition as Mime Type is equal to image/png and move all below actions to the Yes condition (drag and drop will work).

Scenario 2: If you want to move attachments only from Accounts Entity

Add a condition and set Regarding Type is equal to accounts.

Scenario 3: If you want to keep all attachments of a record in a single folder

While creating the file, mention Regarding after the Folder Path.

The above information will help you to replicate the work of PowerAttachment. And if you are looking for more alternative solutions, we have great resources at PowerObjects! We’d be happy to discuss the possibility of a custom solution. For inquiries, please submit a request in our Contact Us Page and it will connect you with our sales team.

Also, if you have ideas for other add-ons being deprecated, add-ons that are still supported, or new add-ons, know that you can always post them in our customer ideas forum: https://ideas.powerobjects.com/.

We look forward to bringing you new and exciting technologies in the near future. Happy D365’ing!

Dynamics 365 – SharePoint Integration

If you have both a Dynamics 365 v9.0 online instance and an online SharePoint instance, you are able to configure these two online tools to work together. This blog will help you through the process.

First, navigate to Settings > Document Management. (Note that your screen may look slightly different, but the options should be the same.)

Next, click on the option for Enable Server-Based SharePoint Integration, as shown below.

A screen similar to the one below will open. On the first page, select Online, and press Next.

On the next page, enter the URL for your SharePoint site in the URL box, and click Next.

The system will verify the SharePoint instance, and that it can be connected to your Dynamics 365.

Setting up SharePoint to Receive Documents

Before you can send documents to SharePoint, you need to set up SharePoint to receive those documents. This means telling SharePoint which entities we will want to connect between SharePoint and Dynamics 365.

To start, click on Document Management Settings to set up your entities in SharePoint.

For each entity you select, a folder structure will be set up in SharePoint for that entity. A list of your entities will appear in the pane. Select all of the entities you want to appear in your SharePoint.

You will also enter in the URL for your SharePoint site again, so it can confirm which SharePoint instance it is creating in.

On the next page, it will confirm your SharePoint, and ask which Entity you want to base the structure on. In our example, we have chosen Account.

When you click Next, another pop-up will appear, letting you know it is creating the folder structure in SharePoint, and that it may take a few minutes (depending on how many entities you are setting up).

The next page will show the progress made for each entity, and when it’s done it will show you which entities were set up successfully, and which could not be made. This process can be done again if you want to add new entities, but taking entities out is far more difficult.

Your SharePoint instance should now be structured to receive documents from these entities.

Making sure the Documents Tab is Set Up

Our next step is to set up the new Documents tab on our forms. To do this, go to a record of an Entity for which you just set up a SharePoint structure.

The integration system is usually very good about setting up the Documents tab automatically, but just in case, click on the Form to edit the form of this entity to make sure the tab is there.

Once the Form Editor is open, click on Navigate. If Documents is in the right-hand pane, drag it over to the appropriate section in the left-hand pane. In our example, the integration system did its job, and set up the Documents Tab on its own in the Common section.

Press Save, press Publish, and close the Form Editor.

Next, we will look at the carat to the right of the record name at the top of the screen. Click on this, and it will bring up your Navigation tabs.

Here is our Documents tab. Click on it.

From here, you can UPLOAD files from your record directly to SharePoint. You should be able to click on OPEN LOCATION to be brought right to your SharePoint instance.

This will take you to your SharePoint instance and the location of the file. From here, depending on your settings, you should be able to download, edit, or upload other files.

Hopefully, this helps you manage and integrate your own instances of Dynamics 365 and SharePoint. Happy D365’ing!

Saving Space in your Dynamics CRM Online Organization

Let's say you've received a notification that your Dynamics CRM Online has reached 80% storage usage. You could choose to purchase more storage, but you may also be wondering if there are ways to reduce storage usage. Below are a few options for saving space in Dynamics CRM.

1. Delete old audit history

If you have enabled audit history, one of the easiest ways to reduce storage usage is to delete old audit history logs. However, depending on your organizational practice and needs this isn't always possible. Generally, as a rule of thumb we recommend deleting audit history older than 6 months. Here are the steps to do it:

  1. Navigate to Settings >> Auditing.
  2. Click on Audit Log Management.
  3. Highlight the old audit log you wish to delete.
  4. Click on Delete Logs.

2. Change audit scope

You may wish to disable auditing for certain fields, entities or workflows to reduce future storage usage. If you are the org system administrator, follow these steps to disable auditing on a specific field:

  1. Navigate to Settings >> Customizations >> Customize the System.
  2. Expand Entities tab on the left-hand side of the window and then expand the specific entity where the field is located.
  3. Click on Fields tab, find the field for which you wish to disable auditing and double click on it.
  4. When the window opens click on the Disable radio button under Auditing option.
  5. Save then Publish.

Repeat this process for all fields you wish to disable auditing for.

To disable auditing for the entire entity, follow these steps:

  1. Navigate to Settings >> Customizations >> Customize the System.
  2. Expand Entities tab on the left-hand side of the window and click on the entity you wish to disable auditing for.
  3. Scroll down and uncheck the checkbox next to Auditing.

3. Delete successful workflow execution log

Another method to save storage space is to delete logs for successfully executed workflows. Note that this will not delete workflow unsuccessful execution logs in case you wish to troubleshoot the error. Depending on your organization's practices this may not be possible, but for those organizations that don't need to store these kinds of records, follow these steps to disable workflow execution logs:

  1. Navigate to Settings >> Processes.
  2. Select All Processes as the View.
  3. Double click on the workflow for which you wish to delete successful execution logs.
  4. You may have to Deactivate the Workflow before you can change settings.
  5. Makes sure that you check the checkbox below

This option is checked by default on background workflows and on real-time workflows this option does not exist.

4. Delete old/irrelevant data

PowerObjects does not recommend deleting data as a method of reducing storage usage. However, in specific cases deleting old or bogus data is a reasonable business decision. If you are debating whether you should delete your data or not, PowerObjects can help you determine the best decision for your business.

5. Move email attachments to SharePoint

One of the common reasons to run out of storage space are large email attachments. Did you know that with the PowerAttachment add-on you can strip email attachments, store them in SharePoint and still maintain the connection between the email message and the email attachment? This is a great solution for those organizations that are concerned about data storage cost, as storing data in SharePoint is about 10 times cheaper than storing it in Dynamics CRM! You can try PowerAttachment free for thirty days and can download it here.

6. Move photo attachments to SharePoint

Similarly, if your organization uses PowerPhoto to store multiple large images per record, you will quickly run out of space in your Dynamics CRM. Just like migrating email to SharePoint, migrating photos need not be a painful process. PowerObjects can  save you money by utilizing cheaper storage location without interrupting your business processes and productivity.

Questions? Wondering what your best options are for saving space? The experts at PowerObjects are happy to help--reach out today!

Happy CRM'ing!

 

Microsoft Dynamics CRM-Driven SharePoint Security

Microsoft Dynamics CRM supports out-of-the-box integration with SharePoint, described in detail two previous blogs: SharePoint Integration in Microsoft Dynamics CRM 2011 and CRM 2011 and SharePoint 2010: Configuration and Folder Structure.

One of the features of out-of-the-box integration is that the folders are created as needed—that is, when user navigates to Documents area of the record for the first time.

This is a usually a good approach, but this method can have shortcomings in some more complex requirements, such as:

Out-of-the-box integration will create a folder using the configured structure, using the name of the record:

Microsoft Dynamics CRM-Driven SharePoint Security

In SharePoint, the security is inherited from parent folder:

Microsoft Dynamics CRM-Driven SharePoint Security

Microsoft Dynamics CRM has robust security architecture, with business units, teams, roles and sharing. In the out-of-the-box SharePoint integration, users that cannot view a record in CRM would be able to view the documents directly in SharePoint.

You could maintain the security manually in SharePoint, but this can become cumbersome with large number of records. Also, SharePoint is often considered as an invisible add-on where users only use the CRM interface. Ideally, you want to programmatically mirror the CRM security in SharePoint.

Our approach to solving this is to use Dynamics CRM plug-ins and create SharePoint folders programmatically, break the inheritance, and add permissions where needed.

Here's the basic functionality of the plug-in:

At this point, all you've done is duplicate the out-of-the-box integration and force it to run at the creation of the CRM record.

The big challenge now is that the required functionalities, BreakRoleInheritance and RoleAssignments, are not available through SharePoint 2010 web services. You'll have to use SharePoint Client Object Model, which requires that the code must reference to Microsoft.Sharepoint.Client.dll and Microsoft.Sharepoint.Client.Runtime.dll. This means the assemblies must be deployed to the CRM server GAC and the plug-in cannot be isolated. Therefore, this approach is not applicable for CRM Online. For CRM Online, you may use similar code, but create your own web service that the isolated plug-in can call.

Here's a step-by-step approach to breaking inheritance and adding access to a specific SharePoint group:

1. Set Client Context and find the List:

ClientContext clientContext = new
ClientContext(site);

clientContext.Credentials = new
NetworkCredential(_connectionInfo["Username"], _connectionInfo["Password"], "");

List oList = clientContext.Web.Lists.GetByTitle(listname);

2. Use CAML Query to find specific folder using URL:

CamlQuery query = new
CamlQuery();

query.ViewXml = "<View Scope='RecursiveAll'><Query><Where><Contains><FieldRef Name='FileRef'/><Value Type='Lookup'>"+FolderURL+"</Value></Contains></Where></Query></View>";

ListItemCollection collListItem = oList.GetItems(query);

clientContext.Load(collListItem);

clientContext.ExecuteQuery();

3. If ListItem found, we can break the inheritance:

oListItem.BreakRoleInheritance(false,true);

4. If you want to add certain access to a group, we can do that against ListItem as well. Here is how to add the Contributer role to a group:

RoleDefinitionBindingCollection collRoleDefinitionBinding = new
RoleDefinitionBindingCollection(clientContext);

RoleDefinition oRoleDefinition = web.RoleDefinitions.GetByType(RoleType.Contributor);

collRoleDefinitionBinding.Add(oRoleDefinition);

oListItem.RoleAssignments.Add(siteGroup, collRoleDefinitionBinding);

clientContext.ExecuteQuery();

With this plug-in, as soon as record is created, the folders are created and security is set:

Dynamics CRM-Driven SharePoint Security

Note that all the items including the subfolders underneath this folder will inherit the permissions from this folder, so you generally only have to do this at one point of each branch.

Microsoft Dynamics CRM-Driven SharePoint Security

Extending from these basic building blocks, you can build a robust, CRM-driven security architecture in SharePoint.

If you want more information regarding CRM and SharePoint Integration, make sure to check also our other blogs:

Happy CRM'ing!

CRM 2013 and SharePoint Integration New Feature

The Microsoft Dynamics CRM 2013 and Microsoft SharePoint 2010/2013 integration remains much as it was in CRM 2011 and is designated as not being a refreshed entity. However, there is a nice improvement in the document location and folder name.

The setup is exactly the same in CRM 2013 as it was in CRM 2011, which you can reference here.

Here is a summary of the setup for a new CRM 2013 deployment:

  1. Download the CRM List Component SharePoint solution and upload the appropriate version (SharePoint 2010 or 2013) in the SharePoint solution gallery.
  2. After successfully uploading and activating the CRM list component in SharePoint, navigate to Settings > Document Management in your CRM 2013 organization.Dynamics CRM 2013 and SharePoint
  3. Follow the same steps for 2013 as completed in CRM 2011 to enable the CRM 2013-SharePoint integration. Your new valid SharePoint site should be listed under your active SharePoint sites.Microsoft Dynamics CRM 2013 and SharePoint Integration
  4. Navigate to a CRM account record and locate Documents in the command bar. You'll be prompted that the folder will be created.


Now for the cool new part. The folder name is no longer simply the account record name—the CRM record's GUID is appended to the folder! You can see that the CRM document location record displays the folder name.

Navigate to SharePoint and see the corresponding folder.

This improvement in the CRM 2013 and SharePoint integration simplifies additional development. It should also should expedite further integration between the two applications, because now SharePoint knows the unique ID of the CRM record!

For other CRM 2013 information, see our full list of CRM 2013 events and educational offerings.

Happy CRM'ing!

Minimizing Data Storage in Microsoft Dynamics CRM

Dynamics CRM is a great tool for many things; tracking sales opportunities, managing cases, and tracking activities. One of the few things that should not be done in CRM: document management and storage.

Many Dynamics CRM customers use SharePoint to store and manage documents, as it integrates smoothly within CRM. In some cases, CRM and SharePoint are hosted in two separate domains. For example: CRM may be Online and SharePoint may be on-premise. Or CRM may be partner-hosted while SharePoint is Online. In these situations, every time a user is in CRM and wants to view the SharePoint documents, they have to enter in their SharePoint username and password. For a company that relies heavily on various documents to operate daily, this is tedious. PowerObjects to the rescue!

We recently implemented a custom SharePoint plug-in that functions as such:

  1. A user logs into CRM and opens an Account or Contact record. (This plug-in can be implemented on any entity within CRM, including custom entities, as long as they have Notes enabled.)
  2. In the ribbon, the user will click on the Add tab and then click Attach File. Then he or she will select the document from the PC.
  3. After the attachment is added, the plug-in kicks off behind the scenes, moving the document to the corresponding SharePoint folder by logging in as an administrator user.
  4. A link to the SharePoint folder is added to the Notes section of the Account/Contact record.

    SharePoint & Data storage in Microsoft Dynamics CRM

  5. The document can also be accessed from the Documents folder in the left navigation of the Account/Contact record.

Not only does this solution prevent the user from having to enter in additional credentials each time they need to add or access a document, it also allows them to stay within CRM and use out-of-the-box CRM functionality (the Add Attachment button) which takes less clicking than adding a document through the SharePoint integration.

If you're interested in a demo, or would like to see if we can provide a solution to meet your needs, contact us.

Happy CRM'ing!

Integrating SharePoint with Microsoft Dynamics CRM Online

SharePoint Online 2013 is part of upgrade to the new Microsoft Portal Online for Office 365 and is part of the Enterprise and Midsized Business plans. With SharePoint Online 2013, you can organize and share team documents, create online knowledge bases and collaborate with your colleagues. SharePoint Online supports the CRM List Component, which allows for the automatic creation of SharePoint folders within admin defined entities for CRM Online. (You can activate a Dynamics CRM Online account from within your Office 365 account, which we will be writing a blog about soon!)

Here are the steps for integrating SharePoint with Microsoft Dynamics CRM.

1. Go to your Dynamics CRM Online account and click Settings, then click Document Management. In the document management section, you will first need to the Install List Component. integrating SharePoint with Microsoft Dynamics CRM

2. This will open a new window, Microsoft Dynamics CRM 2011 List Component for Microsoft SharePoint Server 2013. If you are on either the Midsized and Enterprise business

3. Choose CRM2011-SharePointList2013-ENU-amd64.exe then click Next. This will download a crmlistcomponent file.

4. Save the file to your computer and run. Make sure you know where you saved this to your computer because this will come up in step 4.

5. Go to your company SharePoint site under Sites in the Microsoft Portal Online. Navigate to your Site Settings page. In site settings click Solutions.

6. You will need to upload the crmlistcomponent file you downloaded and saved to your computer. Click Upload Solution, find the crmlistcomponent file and click Ok. Once it has uploaded, the Solution Gallery – Activate Solutions page will automatically open. You must click Activate before clicking close.

7. Go back to the document management page in your Dynamics CRM Online account and click Document Management Settings.

8. In the Document Management Settings page, either type or paste your company SharePoint URL and click next.

9. After adding your company SharePoint URL, you must select your Document Management Settings. To create a folder structure based on a specific entity, click the check box, and select the entity. Folders will be created on SharePoint in the context of Microsoft Dynamics CRM records. After choosing your document management settings create those entities, then click Finish.

That's it!

Happy CRM'ing!

Update to Sharepoint & Issues with List Component in Dynamics CRM

If you have SharePoint integrated with Microsoft Dynamics CRM Online, you may have noticed a recent service update where you now experience the following:

To resolve this issue, you'll need to install the new Microsoft Dynamics CRM List Component for SharePoint Server 2013. You can download the list component from the Microsoft Download Center.

Important:   Only use the new List component after the SharePoint Online service update is complete. To learn when the SharePoint Online service update is scheduled for you, refer to the Office 365 service alert email that you were sent. You can also go to the Microsoft Service Health Dashboard.

Happy CRM'ing!

Use SharePoint Workflows to create CRM 2011 / SharePoint Sub-Folders

Today we'll describe a time-saving trick that automatically creates SharePoint sub-folders to be used in the integration with Microsoft Dynamics CRM.

When configured to do so, Microsoft Dynamics CRM 2011 offers an integration with SharePoint that will create a folder for each record in CRM. Once the corresponding SharePoint folder is created, you can add documents as well as create new folders. If you need the same sub-folders created for each folder, they can be automatically created, rather than having to do it manually.

This automatic creation could be performed by a SharePoint plugin, but SharePoint workflows can also accomplish this task without coding. To do this, you will need SharePoint Designer 2010, and it can be downloaded from Microsoft downloads.

1. First, create two new columns in the SharePoint Account library:

SharePoint sub-folders - Account Library

2. Next, create two workflows to perform the function of sub-folder creation. I've named them as follows:

3. Open SharePoint 2010 Designer and connect to your SharePoint site where CRM integration creates folders.

4. Select 'Workflows.' We will need to create two List Workflows for the Account library:

a. NewAccount_SetStatus

This fires upon creation and is initiated by a user in CRM when the Documents link is clicked for the first time and they accept the prompt to create a new folder.

Step 1 checks to see if the newly created item is a Folder – if not, the workflow stops:


If it is a folder, it checks to see it is one of the two folders:

If it is, it stops the workflow. (We do not want the workflow to create another set below each sub-folder.)

Lastly, the workflow sets a column status field 'SubFolders' to 'Pending':

This fires the second workflow, which reacts to Changes

b. NewAccountFolder_Created

Step 1 of this workflow checks the 'SubFolders' value.

If 'Pending' - this means the newly created folder is a CRM folder, therefore it needs to create the two sub-folders:

The two folders are created and the parent's SubFolders value is set to 'Created'. This indicates that the parent folder has had its children created and will not recreate them if the parent folder is changed:

For the Create Item, use the Folder name to dictate the path, hard-coding the '/Sales'.

Repeat with another Create for the second sub-folder: Technical.

5. Save and Publish the workflows:

Now from a CRM Account record, upon creation of the Account folder, the workflows should fire and create the sub-folders.

 

For other CRM and SharePoint articles, check these out:

Happy CRM'ing!

Bulk Creation of SharePoint Folders and Automated Integration with Dynamics CRM

There are many reasons to use SharePoint with Dynamics CRM: you can store large documents, collaborate with team members and take advantage of the Business Data Connectivity Service. Today, we'll show how you can create SharePoint folders in bulk and then link them to Dynamics CRM. This will save you a considerable amount of time that you would have otherwise spent opening up each record and creating the folders manually.

In this example, we are going to focus on accounts, but these steps can be completed for any entity in CRM.

1. Once you have your SharePoint site configured in CRM, the first step would be to create a map drive to your SharePoint site. There are many different ways to map a drive, but the easiest option is to right click on My Computer and select Map Network Drive. Select the drive letter and enter in the path to your SharePoint site. https://sharepoint.crm.sharepoint.com

2. Now we need to get our list of accounts that we want to create the folders for. Within CRM, go to the Account entity and open the advanced find function. From here you can pull up the active account view and modify the columns only to include Account name.

Bulk Creation of Sharepoint Folders in CRM

3. Run that query and export the list to Excel. Save the file to your local computer.

4. Now open Excel document we just created. We are going to add two new columns.

a. First, create a new column where all it has is a quote. Copy this to each cell.

b. Then create a the following formula:

i. =CONCATENATE(B2,A2,B2)

ii. copy the formula to each cell that has an account value in it.

5. Your end result should look like this.

6. Open Notepad and add the drive letter in which we created the map drive in step 1. Then we are going to change the directory to what entity (folder) we are going to create these folders for. Now we will copy and paste the new column that we create in Excel into notepad. Make sure to save the file with .bat extension. Your file should look similar to the one below.

7. Now run the .bat file. This may take a while depending on the number of folders you are creating.

8. Once the folders are created, the last step is to update CRM with the URL to the specific folder. To do this, we are going to create an on demand workflow.

a. Create the workflow with the following attributes:

i. on demand workflow process

ii. user owned (that way someone won't accidently run the workflow)

b. Then we will add a Create step to create the document location.

i. Select the Relative URL from the lookup

ii. Select the account name for the relative URL

iii. Select the account for the regarding field

9. Now that the workflow has been created, we need to run this for each account. I usually change my personal settings to display 250 at a time. Now select the workflow button from the ribbon and select the workflow you just created in the step above. Once the workflow has completed, you can now go to the documents section in the left navigation to see that SharePoint and CRM are now linked together.

With this simple process, we have now eliminated the daunting task of creating a SharePoint folder for each one of your existing records.

Happy CRM'ing!

CRM 2011 and Sharepoint 2010: Configuration and Folder Structure

CRM 2011 and Sharepoint 2010 Overview

The Microsoft Dynamics CRM List component provides a way to obtain the document management capabilities of SharePoint in Microsoft Dynamics CRM with the appearance and behavior of Microsoft Dynamics CRM. This component also enables  CRM to automatically create document libraries and folders on SharePoint in the context of entities and fields. These folders are used to store documents for  CRM records on SharePoint.

System Requirements:

Supported Operating System

Other Requirements

Folder Structure:

The integration will create folders following the Account or Contact hierarchy nesting child entities and record names below:

CRM 2011 and Sharepoint 2012 Configuration

The folder-driven nature of this integration may not be optimal for all implementations, however using flat (folder-less) views and / or manual linking the user experience may be streamlined.

Benefits:

Considerations:

Configuration:

Navigate to system settings – Document Management – Document Management Settings

This will launch a wizard to select entities that will offer Document folders. This wizard may be re-run at any time to add new entities.

CRM 2011 sharepoint

Structure may be based on entity or simply a folder for every record. Additonally the heirarchy can be driven by either Accounts or Contacts:

Some organization may consider 'Contacts' the Customer so it may be appropriate to use Contact as the heirarchy:

Complete the wizard and creation details will be displayed:

Navigate to the SharePoint site and you will now see the folders for the entities:

Select an Account and click on the 'Documents' link in the left nav bar.

If this is the first time accessing the user will be notified:

The folder is now displayed in a custom CRM iFrame with SharePoint functions:

The pointer for the CRM record to SharePoint folder is a CRM record in the 'Document Locations' entity:

Each folder will have a corresponding record. These can be edited and used in workflow.

The field: 'Relative URL' contains the name of the SharePoint folder:

Back on the Account record, documents may be added using the same steps as if working directly in SharePoint:

Browse and attach

The destination folder will display the designated folder for this record

If the Document library has additional metadata the user will be prompted:

The document is now displayed:

If the library has associated templates they may be accessed from the menu as well:

Launching a new template document also prompts for metadata:

Saving the document will display the familiar save dialog:

Configuring the view to diplay the metadata (in this example a column called: Document Type) will be helpful for the user to locate documents.

The folder location may be edited from the CRM ribbon:

This displays the Document location.

Note: If manually edited the folder must exist in SharePoint.

Child records that were selected to use SharePoint such as Opportunities may also contain documents.

Open the record and navigate to Documents.

Once again a new folder will be created:

Add a document using the same steps used for the Account:

Navigate back to the Account and the Opportunity entity folder is now visible:

Navigate to SharePoint and the folder heirarchy is as displayed:

The complete list of folders can be viewed here.

It may be beneficial to create additional views without the folder structure:

Using the Group By function and the flat view option documents may be grouped by any column:

By editing the Site map these views may be delivered directly from SharePoint:

There you go. Everything you need to know about Sharepoint 2010 configuration and folder structure. If you need help with your CRM Implementation, feel free to contact our CRm Experts.

Happy CRM'ing!010

Displaying an Office 365 SharePoint iframe in CRM

One of the great features in Dynamics CRM is being able to display data or websites from other software packages via an iframe. While working with the Office 365 products, I wanted to display a Sharepoint iframe in CRM 2011. As I accessed the iframe in CRM, I received the message "This content cannot be displayed in a frame".

sharepoint iframe in CRM 2011

With a few changes to the Internet Explorer settings we can make this page display correctly.

  1. Open the internet explorer tools and open the Security tab.

  1. Now select your trusted sites and select sites.
  2. Make sure you have your CRM site as well as your SharePoint site add to the trusted zone.

  1. Once you have your trusted sites setup, then select custom level from the Security tab

  1. Browse about half way down the list till you see the setting for Displaying Mixed Mode. Set this option to "enable".

  1. Select ok and restart your Internet Explorer. Now when you log in the iframe displays correctly.

Hope this CRM tip save you some time!

Happy CRM'ing!