SharePoint 2013 stand-alone installation error: "The SDDL string contains an invalid sid or a sid that cannot be translated"

When installing SharePoint 2013 in stand-alone mode, typical for study purposes, you'll get this error: "The SDDL string contains an invalid sid or a sid that cannot be translated".

I have found the solution in the TechNet article SharePoint 2013 : The SDDL string contains an invalid sid or a sid that cannot be translated: the solution is to share (via Properties | Sharing | Advanced Sharing) the folder Admin_{guid} in C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\.

SharePoint: getTagFromIdentifierAndTitle

When developing in SharePoint using the client-script object model, for sure you have met the function getTagFromIdentifierAndTitle, proposed by Microsoft and copied in many websites.

The basic implementation can be found in many websites, and the article Tags and Identifiers for getTagFromIdentifierAndTitle Function is only one of many examples.


But this function doesn't handle choice fields displayed as radio buttons.

So I have found another other implementation in the blog post Trigger JavaScript Events When a Choice (Radio Button) SharePoint Field Type is Clicked.

SharePoint Item Validation Formulas

I always forget the available formulas used to build SharePoint item validation formulas.

The main formulas are:

  • IF(condition, value if true, value if false)
  • AND(cond1, cond2, condN)
  • OR(cond1, cond2, condN)


Example articles are:

SharePoint: Bamboo Lookup Selector other bugs

Here other bugs I have discovered related to the Bamboo Lookup Selector:

  • if you mark a field as mandatory, then you can't edit the display form (like adding web parts or customizing existing web parts)
    You can avoid this marking the field as not required, modify the form, the mark the field as required
    This is anyway very annoying, because it's time consuming and, in the end, you can forget to reset all the proper fields as mandatory
  • if you mark a fields as mandatory, if you have the Related Fields web part if your display form and you try to add related records, the refresh of parent display form throws an error
    The only solution I have found to avoid this is to market the field as not required and leave it in this way

Sorry but my evaluation of Bamboo Components is of low quality (many bugs to understand and avoid) and not coherence with SharePoint.

SharePoint: Bamboo Lookup Selector bug lists pages

The Bamboo Lookup Selector is a custom lookup field that has (or: would have...) some nice features, like for example filtered selection.

The problem is that sometimes it doesn't work, because of many bugs in the implementation.

In my case, in particular, in edit form the original value is not set correctly in the control. This causes problems to the client, of course, because he is disappointed, when editing an item, to find the values of field changed (because the control in the edit form is not initialized correctly), and has caused me to write additional JavaScript code, in the edit form, the correctly select the correct item.

Anyway, for future reference, here are the bugs lists pages:

SharePoint: how display related (with lookup) records

Since SharePoint 2010, it is possible to customize the OOTB display form of a list item, to display the related items, i.e. the items that have a lookup field pointing to this item.

And in the end the customization is very simple: customizing the list (or content type) display form, it is possible to add the related list directly (and not a ListView web part). And it is possible to customize this list too, through a view, to customize columns to display, sorting and filtering (in addition to the filtering given by the connection to the main record).

A complete example showing this process is displayed in the blog post Showing Related List Items in List Display Form Sharepoint 2010.

Bamboo Calendar for SharePoint: a problem with permissions...

Today I have worked with Bamboo Calendar for SharePoint.

It is nice, its main features are:

  • possibility to merge 2 or more calendars
  • possibility to give colors based on metadata

It has two main drawbacks:

  • it is slow; not slow, it is really very slow;
  • it is not consistent with permission in the SharePoint object model.


About the last point, I explain here: I have an Intranet site where public visitors don't have read access on the site, but only on some lists and/or folders and of course pages.

If I use the OOTB calendar, everything works fine. But with Bamboo Calendar, I need to give read access to the site and read access to the list, even if I want to get data from a folder only.

This is terrible, because it changes all the permission model I had prepared (and that was fitting the reality very well, while now I had to break inheritance in almost all the lists, to protect them) and is less secure because new content will have, by default, public access.

Btw I tought it could be a problem of asynchronous calls (maybe AJAX call when changing month) but nope.


My final evaluation is: not so good, and I would avoid using it, unless explicitly requested by the client (as in this case).

SharePoint: iid attribute of a List View web part

SharePoint renders list view web parts giving an attribute iid for each tr in the resulting table.

The structure of this iis is: contextID,itemID,objectType.

I understood alone the itemID, I was not sure about the contextID (even if I've understood that it was the same for all the rows, so useless) and I was not sure about the objectType, if it was instead the versionID.

Anyway the blog post The magical IID attribute in SharePoint List Views has helped me, together with the jQuery selector to retrieve the itemID:

var id = $(“tr.s4-itm-selected”).attr(“iid”).split(“,”)[1];

SharePoint: comments with history

In SharePoint OOTB it is possible, for multi-line text fields (like typically comments and notes) to enable versioning of changes of the field only (without the need to go to the version history of the item).

For this, it is necessary, first of all, to enable versioning in the list itself (from List Settings, Versioning Settings, Item Version History, Yes).

Then, in the multi-line text field, in the Additional Column Settings, set Append Changes to Existing Text to Yes.