You are currently browsing the tag archive for the ‘SharePoint’ tag.

This post takes you through a step by step scenario on configuring Server-Based SharePoint Integration. Whether you do it for a demo environment, your production or a development environment, as long as you do it for Dynamics CRM Online with O365 SharePoint, the following steps apply.

Assumption is that, as in this case, a new 30-day O365 and CRM Online instance was just spun up. You can do the trial O365 first, then from the admin console add the CRM Online trial, or vice-versa.

The simple way to start is, as soon as your instance is up and running, you will get the notification bar. Click on the Enable Now button.

Read the rest of this entry »

At the Central Administration Level (across the farm)

Open up Central Administration > Application Management

Under “Service Applications” click on Manage service applications


Click on Search Service Application


Under Queries and Results on the Quick navigation click on Scopes

From here on instructions are identical to the steps performed at the Site collection Level.

At the Site Collection Level

Site Actions > Site Settings

Under “Site Collection Administration”, click on Search Scopes


Here you can create new scopes, and edit the custom scopes. Once a scope is created, you have to add rules for crawling.


Pay close attention to how you can structure include/exclude settings to capture only a certain section of a network share:



This is something simple, but I’ve been asked several times about it already, so I’m going to post instructions here on how to achieve this.

Requirement: Store documents and links to documents in the same library


1. Create a Document Library within your site

2. In Library Settings > Advanced Settings enable management of content types

3. Add content type from existing site content types

4. Select and add Link to a Document as a new second content type


5. Start adding content using both content types:


Now you can store in the same document library both Documents and Links to external documents.

Hope this helps, enjoy!

As you’ve probably seen by now, once you create multiple site collections in the same web application, you don’t get a lot of options as far as database location. Well, it’s really not that complicated:

  • Create the databases for the new site collections (easy enough in CA)
  • Run the following PowerShell command for each site collection, or put it in a script if you feel like it:

Move-SPSite <YourSiteURL> –DestinationDatabase <ContentDBName>

That’s it, easy as pie. See more information on TechNet:


Part of SharePoint 2010, a new tool was added to made life easier: the developer dashboard. By default disabled, you can enable it multiple ways:


stsadm –o setproperty –pn developer-dashboard –pv ondemand

Using PowerShell:







Write-host(“Level:” + $contentSvc.DeveloperDashboardSettings.DisplayLevel)

Values available to be set for the developer dashboard:

  • On
  • Off
  • OnDemand

Using code:

SPWebService srv = SPWebService.ContentService;

srv.DeveloperDashboardSettings.DisplayLevel = SPDeveloperDashboardLevel.OnDemand;


NOTE: using SPFarm is not supported in the final release of SharePoint.

Happy debugging!

MVP Reconnect

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 617 other followers

Follow Dynamics 365 Wizardry on