Skip to main content

SharePoint 2010 - Real Search Scenario

The main thing in SharePoint development is not how to implement some piece of functionality but is the approach correct. And defining the approach is something very difficult which required experience and time.
It also required reviewing other scenarios and implementation.
So in some posts, I'm going to explain one real scenario that we have in our company  and the approach that we implemented.

The scenario:  creating document management system that will live in many site collections in one web application.

It may sounds simple - but it's not. It's a very very serios and difficult application.
And what I want to share with you is where the SharePoint 2010 Search take part. It helps us in:

      1. Webparts showing cross site collection data
      2. Finding documents and item based to our custom fields and custom content types

And while point 2 sounds absolutely normal - of course search is for searching items, point 1 is very tricky part of implementing such scenario.
I'll describe in detail the two points and the difficulties in the approaches in the next weeks.

However, the search is not in the first steps while building one application. Before that usually the development go through other things: In our project we firs build:
     - custom site definitions - base on the publishing portal; important part if we plan to create sites programmatically;
     - custom contenttypes - extremely important part; help managing the metadata and give us the ability for
            custom Add/Edit forms
            validation of the user input
            easily finding data in search results
      - webparts for retrieving data
      - workflows  - defining the live of the documents

And  then came the search functionality which will be main topic in my next posts.

...

Comments

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed.
The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before.
There is a new control called ClientPeoplePicker.

How to use it:
1.Add this references

<%@RegisterTagPrefix="wssawc"Namespace="Microsoft.SharePoint.WebControls"Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
2.Add the following control declaration


      <wssawc:ClientPeoplePicker Required="true" ValidationEnabled="true" ID="peoplePicker" runat="server" InitialHelpText="<%$Resources:wss,aclinv_PickerIntialHelperText%>" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="false" CssClass

The column name that you entered is already in use or reserved. Choose another name.

The problem: 
You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name."



Why this is a problem?
Because you need to create custom columns and content types using the default SharePoint interface.
And the business users have to see properly named columns - for example "Description", not "My Description".

Solution:
It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):
 - it supports columns with same Display Names.
 - you can’t have columns with same Internal names

Let’s implement the following common scenario:
You are creating a SharePoint customization and you need the following column:
   Type: Multiple lines of text
   Internal Name: MyProjectDescription
   Display Name: Description

 Here is the correct way to achieve it:
1. Create the column MyProjectDescription.
This will create column with I…

Office 365 Migration API: how to migrate the taxonomy metadata

If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage.

In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API.

The scenario I'm going to use is simple - migrate single Document library with single document.
The document has one taxonomy column (MyTaxonomy) and three versions:

Here are the steps:

Step 1: Export the document library

Export-SPWeb "https://portal.cosingens.com/" ` -ItemUrl "/Shared Documents" ` -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4
This command will export the document library and will create the initial package.
The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the server side obje…