SharePoint Development

Compare SharePoint 2013 editions

noreply@blogger.com (Komakino) — Sun, 28 Apr 2013 20:35:00 +0000

A quick reference for comparing the several editions
(Office 365 plans, standalone plans & on-premise)

SharePoint Developer, Design and Testing Tools

noreply@blogger.com (Komakino) — Tue, 23 Apr 2013 18:09:00 +0000

A nice overview of several tools...
Other tools I can think of:

If you know an awesome tool, which is not included in the lists above? Please leave a comment...

Crawling publishing image fields

noreply@blogger.com (Komakino) — Thu, 18 Apr 2013 18:42:00 +0000

When you crawl an image field in SharePoint 2010, you will notice that its crawled property does not contain any data. You have several options to work around this issue, but my favourite option is by using a custom META tag. The SharePoint crawler will provide every META tag as a crawled property. These crawl properties can be found below the Categories > Web section in the Managed Properties module of the search service application. These properties are available with the same name of the custom tags, in uppercase.


 
   <meta name=’myImageFieldMetaTag’ content=’<SharePointWebControls:FieldValue  FieldName="myImageField" runat="server" id="myImageFieldId"/>’ id="myImageFieldMetaTagId" />

What about SharePoint 2013?

I haven't tried it yet, but it seems like it's supported in the new version.
All site columns that contain values will automatically become managed properties when they're crawled. A publishing image field is one of them and will be crawled with the following name syntax:

Crawled property name: ows_q_IMGE_SiteColumnName
Managed property name: SiteColumnNameOWSIMGE

I'm not sure yet, if I like the auto generation. Those names are not that userfriendly, but yes... it doesn't matter in this case.

Reference: Automatically created managed properties in SharePoint Server 2013

No sitecollections available in content database

noreply@blogger.com (Komakino) — Fri, 12 Apr 2013 13:52:00 +0000

After a content database restore we coudn't access our sitecollection anymore. We verifed the content database status and number of sitecollections. In our case, the current number of sitecollections was equal to 0.

We fixed this by running a couple of Powershell commands...

1. Retrieve content database GUID

Get-SPContentDatabase

2. Synchronizes the content database with the configuration database of the farm with respect to what site collections actually exist in the content database

$cdb = get-spcontentdatabase -Identity [insert guid of contentdatabase here]
$cdb.RefreshSitesInConfigurationDatabase()

Reference: MSDN

Display specific managed metadata in refinement panel - SharePoint 2010

noreply@blogger.com (Komakino) — Mon, 08 Apr 2013 20:57:00 +0000

Another blogpost about SharePoint 2010? Yes I know, it's time to move on... but hey, not every customer has already the new version of SharePoint. This information is not really unique on the web, but it's more a reminder for myself ;)

The refinement panel webpart's FilterCategoriesDefinition property contains the XML that specifies the filter categories. If you want to modify the categories, don't forget to clear the "Use Default Configuration" checkbox.

Display all managed metadata fields

Display only specific managed metadata fields
Place the following XSL stylesheet into the XSL property of the refinement panel to view the raw XML, returned by the search...


  
  
   
   
   <xsl:copy-of select="*"/>

The raw XML outputs the different filtercategories. Each filtercategory has a specific ID with prefix 'Metadata_xxxxx'. Copy the last part of the ID (i.e. 'xxxxx') and use this value to set the title of the category within the filter category definition section:

SharePoint 2013 meets a new Global Assembly Cache (GAC)

noreply@blogger.com (Komakino) — Thu, 21 Mar 2013 22:43:00 +0000

As a SharePoint developer you need to muddle in the Globale Assembly Cache (GAC) from time to time. Be aware that SharePoint 2013 now uses a different CLR (v4.0).This means that the GAC directory is moved from c:\windows\assembly to c:\windows\microsoft.net\assembly.

If you don't find your assembly in the GAC - think twice!

Hide list column headers of a list view webpart

noreply@blogger.com (Komakino) — Sun, 28 Oct 2012 08:27:00 +0000

Hide list column headers of all list view webparts on the page

Add a Content Editor WebPart (CEWP) to the page

Use the following CSS:

Hide column headers of a specific list view webpart

The method, described in the following blogpost will definitely work (find listview by title), but there is a downside with this method. What if the end user renames the list? Our solution will break.

I think it's safer to find a listview by URL. The URL is fixed and cannot be changed from the UI (only with SharePoint Designer).

Add a Content Editor WebPart (CEWP) to the page
Use the following JQuery script: !! Don't forget to change the URL to the URL of your list

SharePoint 2013 - Short Introduction to Animation Engine

noreply@blogger.com (Komakino) — Sat, 20 Oct 2012 10:23:00 +0000

Already noticed the "fade in" effect on the page while browsing in SharePoint 2013?
No? Open a standard Teamsite and focus the main content...

Before

After

So, how does this work?

Some site templates uses the Minimal Download Strategy (MDS) framework. This framework consists of several components working together to only download the changes between the different pages. The main component is the start.aspx application page (as I said, there are more components to make this work). This page is responsible for loading pages from the site using the MDS. I don't want to write an in-depth article about MDS here...our main focus is the animation effect, remember? :) The codebehind of this page is defined in the following class: Microsoft.SharePoint.ApplicationPages.MDSStartPage.

The startpage will, among other things, register the start.js script. This script contains a javascript object, called the AsyncDeltaManager. This object will handle the delta requests/responses. When the AsyncDeltaManager retrieves a delta, he will call (at the end) the BeginTransitionAnimation() javascript function. This function does the preparation for the animation effect, ONLY if the MDS animation is enabled. At the end, the animation effect will be started in the EndTransitionAnimation() function. This is where the magic happens. He will call the SPAnimationUtility.BasicAnimator.FadeIn(content, null, null); command!

As far as I know, the fade effect is only used for the following placeholders:

PagetitleInTitleArea
Main

Can we disable the animation effect?

Yes, we can! (HTML5) web storage is used to enable/disable the animation effect. Below you'll find a couple of commands you can use...

SPAnimation.Settings.EnableAnimation(); //enable animation
SPAnimation.Settings.DisableAnimation();//disable animation
SPAnimation.Settings.DisableSessionAnimation();//disable animation only for this session
ToggleAnimationStatus();//toggle animation
SPAnimation.Settings.IsAnimationEnabled(); //check whether animation is enabled

Cross post: Solutions Model VS Apps Model in SharePoint 2013

noreply@blogger.com (Komakino) — Fri, 19 Oct 2012 16:36:00 +0000

A nice comparison sheet between the different models: Multifaceted In-depth Comparison of SharePoint 2013 Apps vs Solutions Code Models

Display animated spinner while loading modal dialog

noreply@blogger.com (Komakino) — Mon, 15 Oct 2012 13:26:00 +0000

The following javascript function SP.UI.ModalDialog.showModalDialog(options); is a way to display a modal dialog with specified dialog options. When you assign a value to the URL property of the dialog options, an IFRAME tag is rendered pointing to the appropriate URL.

ShowDialog example

var options = {
    title: "My Dialog Title",
    width: 400,
    height: 600,
    url: "/_layouts/DialogPage.aspx" };

SP.UI.ModalDialog.showModalDialog(options);

To display an animated spinner, you can set a background-image for the iframe with some CSS.

CSS

iframe
{
    background-image: url("../images/animatedspinner.gif");        
    background-repeat: no-repeat;     
    background-position: 50% 50%; 
}

Result

Extract details from a WebException

noreply@blogger.com (Komakino) — Wed, 01 Aug 2012 16:30:00 +0000

try
{
    //Do something
}
catch (WebException ex)
{
    using (var stream = ex.Response.GetResponseStream())
    using (var reader = new StreamReader(stream))
    {
        string errormessage = reader.ReadToEnd();
    }
}
catch (Exception ex)
{
    //Do something
}

Easily embed Youtube videos, Javascript, styles and other markup into a SharePoint 2013 page with the Script Editor WebPart

noreply@blogger.com (Komakino) — Mon, 30 Jul 2012 21:17:00 +0000

Instructions below are executed within a Team Site template:

Select the ‘Edit’ icon in the top right corner of the page to edit the page
Select ‘Page’ in the ribbon, click ‘Embed Code’
Enter some script, styles, embed code,… in the editor box

Javascript example

Youtube example

Notice the preview of the embedded video
Click ‘Insert’
Save the page with ‘Save & Close’ in the top right corner.

Some remarks:

After clicking ‘Insert’, a Script Editor WebPart will be automatically inserted into the page - only if you’re using embedded code.
Default Chrome type is ‘None’
The Script Editor WebPart is also available as webpart under ‘Media and Content’
You can still use the Content Editor Webpart to achieve the same results. The main difference between the two is that the Content Editor WebPart is more focused to enter rich text content, while the new Script Editor WebPart is more focused to insert HTML snippets and scripts.

SharePoint Sucks – And Here’s Why...

noreply@blogger.com (Komakino) — Sat, 23 Jun 2012 11:45:00 +0000

What would you do when you see this message?

A) Stay calm, try to copy the correlation ID, notice that you can’t copy it and still stay calm, write it down on a piece of paper and track it in the ULS logs

B) Open your browser, go to a search engine and type “SharePoint sucks” to let off steam

If you have chosen option B, you’ll probably encounter the funny blog series of Bjørn Furuknap. Give it a read, they are a bit outdated but there’s still a lot of truth in it.

Ow, btw, I didn’t search after “SharePoint sucks” – it was a colleague who mentioned the blog series. He has probably chosen for option B. Ok, to be honest, there are days that I hate SharePoint too. I have some sort of love/hate relationship with it.

Let me end this post with a funny quote of Bjørn Furuknap.

Over the past couple of weeks, I’ve said quite a lot of things about SharePoint that may lead you to think I hate SharePoint. I don’t. Quite the contrary, I love SharePoint. Yeah, it sucks, but so does my wife, and I’ve married her twice.

Quick Tip: Approval Workflow - Due date for all tasks

noreply@blogger.com (Komakino) — Sun, 17 Jun 2012 08:24:00 +0000

Within the association form of the approval workflow you are able to set the “Due Date for All tasks”. This setting specifies the date by which all tasks are due.

What if you want tasks to become due on a specific time on a specific day? In the user interface of the association form you are not able to specify a time value.

Although it is nowhere documented, it is possible.

For example, if you want to terminate all tasks on the 18th of June at 13h30 you can set the following value in the textbox:
2012-06-18T13:30:00

Use the following structure to set a time value:
yyyy-mm-ddThh:mm:ss

I know, it’s not really user friendly, but it works. You can probably use SharePoint Designer to tweak the association form to implement some extra logic.

One of the best references online about approval workflows in SharePoint 2010: All about approval workflows

Export Farm Solution Package with PowerShell

noreply@blogger.com (Komakino) — Wed, 29 Feb 2012 11:48:00 +0000

Follow the steps below to export a farm solution package…

1. Open a text editor – such as Notepad.
2. Paste the following code snippet:

$farm = Get-SPFarm
$file = $farm.Solutions.Item("MySolutionPackage.wsp").SolutionFile
$file.SaveAs("c:\MySolutionPackage.wsp")

3. Replace the highlighted text above with the name of your solution package.
4. Save the file - give the file a name and save it with the extension ps1 (eg. extract.ps1) and place the file on the C:\ drive.
5. Open the SharePoint 2010 Management Shell
6. Navigate to the location of the script and execute it.
7. The solution package will be available on the C:\ drive

Update: If you want to download all the solutions at once you can use the following script:

$dirName = "C:\Solutions"
foreach ($solution in Get-SPSolution)
{
$filename = $Solution.SolutionFile.Name
$solution.SolutionFile.SaveAs("$dirName\$filename")
}

Error: The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service...

noreply@blogger.com (Komakino) — Thu, 16 Feb 2012 19:18:00 +0000

This error can be encountered while viewing an InfoPath form in the browser. In most cases, the problem can be solved by reading through the following blogpost.

In my case, the state service was enabled and the service application was correctly associated with the webapplication. I solved this by deleting the 'corrupt' state service database, creating a new one and attaching the new database to the farm - all these steps can be done with some Powershell commands.

Remove-SPStateServiceDatabase
New-SPStateServiceDatabase
Mount-SPStateServiceDatabase

Reserved Querystring Parameters In SharePoint

noreply@blogger.com (Komakino) — Fri, 09 Sep 2011 16:18:00 +0000

This is probably the 100th post on the net about...

"Be careful when naming querystring parameters in your SharePoint applications"

But you can't say it enough. They cause trouble!

For more info read this.

Could not access the Search administration database. A generic error occurred while trying to access the database to obtain the schema version info.

noreply@blogger.com (Komakino) — Wed, 07 Sep 2011 09:05:00 +0000

Deleting the following registry key - did the trick for me:

“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS\Services\Microsoft.SharePoint.Search.Administration.SPSearchService”

In fact, it's just one of the things that need to be verified.
Read this post for more info.

Default location picture upload in RTE

noreply@blogger.com (Komakino) — Sat, 11 Jun 2011 13:55:00 +0000

If you want to insert a picture in the rich text editor directly from your computer, you will notice that the RTEUploadDialog pops up in which you can browse for a file and select a location.

Unfortunately, you can’t set the default location.

Workaround

Option 1: Because the “Upload to” dropdown list is filled up alphabetically, you can rename the library you want (eg. let it start with an underscore).

Option 2: (Not supported by MS) You can write some javascript to select another default value for the dropdown list. Insert your javascript into the RTEUploadDialog application page (/_layouts/RteUploadDialog.aspx).

As far as I know, this page is not only used for uploading images, so you probably have to take into account the querystring parameter ‘Dialog’ (/_layouts/RteUploadDialog.aspx?LCID=1033&Dialog=UploadImage).

Reporting Services: RSViewerPage

noreply@blogger.com (Komakino) — Mon, 11 Apr 2011 06:13:00 +0000

The main file used for displaying reports is the RSViewerPage.aspx. This page contains a breadcrumb and a webpart called ReportViewerWebPart. This webpart renders a toolbar, the report and a parameters pane.

Hide buttons from the toolbar

I saw a couple of articles of people who disable some toolbar buttons by diving into the ConfigurationInfo table of the Reporting Services Database. This method will work for a few buttons, but not for all of them. I discovered that you don’t need to adjust that database table at all. You can use the ToolBarItemsDisplayMode property of the ReportViewer WebPart. This property allows you to hide/show specific parts of the ReportViewer’s toolbar. Be aware, this property is an enumeration field.

For example: ToolBarItemsDisplayMode=’223’ will hide:

Open with Report Builder (Action Menu)
Subscribe (Action Menu)
Atom icon

Before:

After:

Why 223? You have to make the sum of the values of the parts you want to include in the toolbar. The values are shown in the reference table below:

You can set the property by adding the property in the RSViewerPage.aspx like

<RSWP:ReportViewerWebPart id="m_sqlRsWebPart" runat="server" SuppressWebPartChrome="true" Height="100%" ToolBarItemsDisplayMode="223" Width="100%" />

You can pass the property as a querystring rv:ToolBarItemsDisplayMode=”223”

Ogone – Feedback Parameters

noreply@blogger.com (Komakino) — Thu, 10 Feb 2011 20:43:00 +0000

The merchant can send some extra parameters in the hidden fields of the order form, in order to retrieve them as feedback parameters after the payment.

One of the hidden fields is the PARAMPLUS parameter. This field submits some parameters and their values you would like returned in the feedback request (as a querystring).

Be careful when you generate your SHA-OUT hash based on the incoming feedback parameters. You have to exclude all the extra parameters, you sent with the PARAMPLUS parameter, before generating the hash.

SharePoint Designer 2010 Action: Start Approval Process

noreply@blogger.com (Komakino) — Wed, 19 Jan 2011 07:21:00 +0000

The “start approval process” is a brand new workflow activity available in SPS 2010.

The Start Approval Process action behaves like a pre-built workflow—the logic is already defined in the action. The action has several different phases built into it that defines task behaviors, task process behaviors, logging to the History Log, e-mail notifications, and completion conditions. Although the action comes with pre-built logic, it still needs information from you—such as the users (the reviewers), the order in which the tasks are to be routed to the participants—serial or parallel, the default is serial, and the due dates for task completion.

You can customize the predefined logic within the activity by clicking on the ‘approval hyperlink’ (as shown below).

A quick example:

The out-of-the-box approval workflow includes the following settings in his association form: End on first rejection & End on document change.

As far as I know, you can’t set these settings by default in this activity. If you want to apply this behavior to your own build workflow you can, for example, customize your initiation / association form with two extra checkboxes and pass the values to the workflow or you just can remove the condition so that they’re ‘checked’ by default. The screenshots below give you an idea of how to (remove the ‘if clauses’ way) enable this behavior.

You can find the behavior of the End on first rejection in the ‘change the behavior of a single task’ section.

First, move up the logic within the condition. Then you can remove the condition.

You can find the behavior of the End on document change in the ‘change the behavior of the overall task process’ section.

First, move up the logic within the condition. Then you can remove the condition.

That’s it.

Slidedecks BIWUG on SPS2010 WCM and FAST Search 2010 available

noreply@blogger.com (Komakino) — Fri, 10 Dec 2010 13:14:00 +0000

You can find them here.

Getting started with the Client Object Model in SP 2010

noreply@blogger.com (Komakino) — Fri, 10 Dec 2010 12:38:00 +0000

Some useful resources to get started the with the Client OM...

How To: exclude welcome pages in search results

noreply@blogger.com (Komakino) — Wed, 25 Aug 2010 11:52:00 +0000

Remember there was a ‘welcome page search retrieval’ issue in SP 2007? If not… take a look at http://svengillis.blogspot.com/2009/02/no-searchresults-for-content-available.html

Fortunately, this issue has been fixed in SP 2010. In some cases, you still want to exclude welcome pages in the search results – just like in the old days.

To do this - follow the steps below:

Navigate to the Search Service Application
Make sure you did a full crawl on your content source
Create a new rule in your search scope (all sites or whatever) as follow:

By creating this rule you’ll eliminate the site URL (eg. /news) items. At this moment, the site default page URL is still included (/news/pages/default.aspx). In the next step we are going to eliminate them too…
Create a new Crawl Rule
Make sure you’ll do a full crawl again and that the Search Scopes are updated
Notice that no welcome pages are found in the search results