Skip to main content

Integration in Internet ?

Nowadays, the business need of system integration in one company become more and more important task. Many companies search for good, cheep and easily developed portal solutions so they can make one common entry point for their systems and no doubt, the best Microsoft solution for this task is the SharePoint platform.

While companies and enterprise integration have many options and products, what about the Internet integration? Is there a simple and no resources required way to recreate the idea of integration?

The reason for trying to do this is the fact that there are many areas in internet where we can make a portal collecting different sources and information and making this in a very simple and cheep way. And of course, if we make good and useful portal, this will not be a waste of time ad money.
Making or using some crawlers and displaying the results in categorized way is good but not so cheep solution.
As a big fen of Google, I try to combine their services and to see how can I recreate the idea of integration. 
I get for example my personal "web systems"- two blogs, facebook profile, personal web site. And the picture is something like this:

The personal site will be the user entry point and will have RSS from the blogs and facebook profile. The data storage will be the Picasa (for images) and files) and the monitoring will be Google Analytics.

Actually, the example is not very clear but the idea of iterating things is really good concept and it's worth to be experimented with it.
And to best thing is such approaches is that we don't replace the existing systems ( in many case this is impossible), we just combine them and get to the user better experience and analytics data.



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=, 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".

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 "" ` -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…