While researching MySite Permissions I found the following table online that I think will be nice to Blog for future reference. The table describes how the combination of User Profile Service permissions influence the Users experience in the MySite.

5fdd6fb2-ff07-467e-a617-4d188ffb6e70|2|5.0
Got this error after creating some taxonomy fields and then importing them into Visual Studio using CKSDev. If I then tried to connect a term to the taxonomy field the error occured.
(“The object has been updated by another user since it was last fetched”)
This did not happen at first, but only after removing my Development Site Collection, and then deploying again from Visual Studio to a new clean sitecollection.
The error was thrown because there was a version number specified in the field xml of the taxonomy field. More detailed information can be found at: http://www.mpspartners.com/2012/02/SharePointTaxonomyFieldandTheobjecthasbeenupdatedbyanotherusersinceitwaslastfetched/
e25e3dd2-ef6c-44ba-a247-eac2fa0d4298|0|.0
Let say we have a publishing page, and we create a link on that publishing page to the NewForm of a List.
Aftre the user created the listitem we would like to go back to the page the user clicked the link, in stead of the list overview page.
When you want to return to the page you came from, sharepoint uses a QueryString Parameter called "source".
Microsoft was even kind enough to provide us with al small javascript function to automatically add this parameter to a Link.
In a content editor webpart u can use
<A onclick="GoToLink(this);return false;" href="/feedback/_layouts/listform.aspx?PageType=8&ListId={B0EF9608-FC48-401E-9343-4EDDF4585131}&RootFolder=">new feedback</A>
--update--
If however you are in a Publishing page Content Field, SharePoint is kind enough to strip all javascript from the contents.
So you will have to manually add the source parameter for that link.
GoToLink is located in the core.js
9de28790-d692-4abd-b2de-9924fe4e2f91|1|2.0
Found out today that the behaviour of the PublishingWebControls:EditModePanel changed between MOSS2007 and SP2010.
Apparently,now in SP2010, you need the EditItem Permission to be able to see what is in an EditModePanel even if the PageDisplayMode attribute is set to "Display".
So basically it works like a SPSecurityTrimmedControl
Example:
<SharePoint:SPSecurityTrimmedControl PermissionsString="EditListItems" runat="server">
</SharePoint:SPSecurityTrimmedControl>
Update
This behaviour has been changed back to 2007 behaviour as of SP1 for Sharepoint 2010
5603cb67-ffb1-44da-a61d-6f89b92c480c|0|.0
I keep losing this really handy xsl for displaying the raw search result XML in SharePoint. Blogging it for future reference :).
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="/">
<xmp><xsl:copy-of select="*"/></xmp>
</xsl:template>
</xsl:stylesheet>
a7ae29f3-7e88-4bfa-a5bb-9612b349bd59|1|2.0
When you upgrade to Microsoft SharePoint Server 2010, some of the new SharePoint Enterprise Search Web Parts are missing from the Web Part gallery for upgraded site collections.
The following are the missing Web Parts:
-
Refinement Panel
-
Related Queries
-
People Refinement Panel
-
Dual Chinese Search
This topic describes how you can add these Web Parts to the Web Part galleries of the upgraded site collections.
Another post about this with more detailed problem information
b6398334-85cc-4631-93d7-4e6df661b995|1|5.0
Today I waisted some time installing Windows 7 on my new Lenovo W510.
It has 2 HDD's so I could not use a win7 DVD. No problem there.
Borrowed a USB stick from a collegue (Thnx Jan) and downloaded this little tool. This allows you to copy an ISO of Windows7 to a USB drive and install it from there.

After copying the windows7 files to the USB drive I was ready to get started. So I put the drive in the side USB ports of the W510 and gor started. 30 minutes and lots of error messages later I decided to BING it.
It turns out you cannot install the laptop with a external USB drive (or USB dvd player) on any but the rear usb.
I guess that this port is on another controller that is supported by default and the side (USB 3.0) ports are on another controller that is not.
Just thought I would put it out there for everyone else
4b2692c9-4dc2-4022-a4fa-501bf6a2ffaa|3|5.0
The issue occurs on a publishing site that has a contenttype containing a Publishing Hyperlink (SPFieldLink).
Inserting a link with the Link Tools Tab of the ribbon works fine, but removing the link after it has been set does not.
Found a post on Stackoverflow that describes the issue in detail:
For quick reproduction: (steps and testing by M. Siepel)
- Create a Publishing Portal site
- Create a column of type Publishing Hyperlink
- Add the column to de Welcome Page contenttype
- Navigate to the Press Releases page
- View information -> Edit
- Add a link to the newly created column and save the page
- Open it again, remove the link (the link is visually removed, it even says: Click here to add a new Hyperlink)
- Save the page again
- Now open the page again.
- In our situation, the message 'Click here...' is gone, and if you view the source our original link is still there, but there is no text inside it.
I did some testing on it and these are the results:
- It occurs on dev and prod server with a custom solution installed
- It occurs on a server with no custom solution installed (clean install)
- It also occurs on the 'Adventure Works' site (both on a clean install and on a server with custom solution)
- It occurs both when creating a sitecolumn of type Publishing Hyperlink through API and UI
- When viewed with firebug the 'deleted' link is still in the href property, but the text property is empty
- Tested on IE/FF
- When viewing with Sharepoint Manager 2010, the link is still in de DB (with no text property as stated above)
- It happens on Dutch and English sites.
A little more time on the Bing machine resulted in finding a post from M Siepel on the Microsoft forums:
http://social.msdn.microsoft.com/Forums/en-AU/sharepoint2010general/thread/8ce468ec-096b-4ad2-a1e9-0bfb93cecf95
Basicly it states that the bug can be reproduced consistently and it has been reported to the product team. Lets hope this will be fixed in the next CU.
Someone already created a powershell fix, but that is not really end-user friendly. I will update this post
Param([string]$site0=http://mysharepoint,
[string]$list0="My List",
[string]$itemKey0="Item Key",
[string]$linkUrl0=http://newlink,
[string]$desc0="New description",
[string]$toolTip0="New Tooltip")
$site = Get-SPSite($site0)
$rootWeb = $site.rootWeb
$lists = $rootWeb.Lists
$list = $lists[$list0]
$items = $list.Items
$listItem = $items | Where-Object {$_.Name -eq $itemKey0}
$linkUrl = $listItem["Link Url"]
$linkUrl.NavigateUrl = $linkUrl0
$linkUrl.Description = $desc0
$linkUrl.ToolTip = $toolTip0
# this is the trick - set the object back to listItem
$listItem["Link Url"] = $linkUrl
$listItem.Update()
cdfa2c88-c814-4f4d-a9ed-11dc36634130|0|.0
About a week ago Microsoft published the XML Schema Definition (XSD) files for the Microsoft Visio 2010 XML Drawing (.vdx) format. This schema is also known as DatadiagramML.
This should make it alot easier to use the visio file to generate code based in the visio file.
The DatadiagramML Schema for Visio 2010 consists of three .XSD files:
- visio.xsd is the core schema used by Visio 2003 and later
- visio12.xsd is the set of extensions used by Visio 2007 and later
- visio14.xsd is the set of extensions used by Visio 2010
More information about the schema is available in the Visio 2010 XML Schema Reference on MSDN.
9aedc9fb-fc67-468f-a6d7-5ce9a463eb13|0|.0
I missed these when they where released
28 April Sharepoint Foundation CU
http://support.microsoft.com/kb/2512804/en-us
11 March Sharepoint Foundation CU Hotfixes
http://support.microsoft.com/kb/2475880/en-us
28 April Sharepoint Server CU
http://support.microsoft.com/kb/2512800/en-us
def34aa7-1b27-473f-a075-62d158069cbb|0|.0

At e-office we have been working hard at baking our Microsoft cake this year
Lets just say we are pretty serious about our baking skills.
To put the cherry on top we are submitting a great case to the anual Microsoft World Partner Conference in LA.
8b033153-ef13-4d8d-882a-281c3c318cce|0|.0