Skip to main content

What is SPObject.Resolve()

This is my professional blog where I will post things, thoughts and ideas that I face in my daily work as a developer. And because I’m a SharePoint developer most of the topics here will be about SharePoint 2010 and integration of applications.

In short about me :
   - at this moment I have 3 years of experience as a developer and have worked in the following companies:
        Interconsult Bulgaria
        ( April 2010 to present )
        Vereo
        ( September 2008 to April 2010 )
        Telerik
        ( February 2008 to May 2008 )
        Weblancers
        ( June 2007 to February 2008 )

   - I have developed Windows Froms and ASP .NET applications but my interests and passion are in building SharePoint solutions

   - I have 3 certificates for SharePoint - although I don’t think MS exams are something really important I think a developer who pretend to be a good professional has to take the exams in his area.


Why to have a blog ?

SharePoint is area where is very difficult to write or show something really new. Of course, if you are a MVP or guy from MS SharePoint team you can but in the other cases – it’s really difficult.
Even though having a professional blog is important. This is the stage to show your ideas, problems and thoughts. It’s a test for yourself to understand whether you are able to write interesting and important topics or not and of course, this is a way to build your unofficial CV showing your way of thinking and personal progress. And of course, to make your English and way of writing better.

So ….

    try
    {
          SPObject.Resolve()
    }
    catch(Feedback fd)
    {
           PersonalUpgrade.Load(fd);
    }
    finally
    {
           ShareThoughtsAndIdeasToFindWhereTheRightDirectionIs();
    }


. . .

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…