Bolufer Blog - SharePoint & .NET language

In SharePoint 2013 on-premises, there is a confusing user experience with the ability to “share” documents for visitors and members unless you have set up outgoing e-mail on your farm and enabled access requests for your site. While the Share option is not available in the document ribbon for visitors and members, it is visible from the list item dialog as shown in Figure 12-13. Clicking the Share option in this scenario without access requests and e-mail enabled returns an error message: “Sorry, something went wrong. Only a limited set of people are allowed to share this content.” This is actually by design, though the error message is a little confusing. Nothing really went wrong; the user just doesn’t have permission to share a document if the site doesn’t have “Allow access requests” turned on . This capability is enabled in Site Settings > Site permissions, and when enabled, it allows visitors and members to initiate an internal document-sharing request that goe...

Esto solo funciona si SOLO hay un calendario en la página, para varios hay que jugar con el id del calendario. Con el fiddler hay que recuperar la variable ret de la última devolución del picker, para ello hay que situarse en la sección de response, decodificar el texto y recuperar el texto en la pestaña textview. //Ocultar Añadir recursos <style> .ms-acal-entity div { display:none; } </style> //Que aparezcan todos los recursos disponibles  -- OJO con las comillas -- <script type="text/javascript" src="http://intranet/Reserva/SiteAssets/jquery-2.0.3.min.js"></script> <script type="text/javascript"> function _setDefaultResources() {       var el = $(".ms-acal-rootdiv"); var xml = "\u003cEntities Append=\u0022True\u0022 Error=\u0022\u0022 DoEncodeErrorMessage=\u0022True\u0022 Separator=\u0022;\u0022 MaxHeight=\u00223\u0022\u003e\u003cEntity Key=\u0022Altaveus\u0022 DisplayText=\u0022Altaveu...

One of the most common questions is definitely about the resources used by Search. Using Continuous Crawl and/or many crawl processes and/or frequent crawl schedules and/or big change sets in the content sources, etc. – all makes the resources consumed by Search higher and higher. Besides the most known optimization and scale-out techniques, I get the question very often: how the resources consumed by noderunner.exe can be limited? The first part of my answer is: Please, do plan your resources in production! Search is often seen as "something" that works "behind the scenes", but it can make some very bad surprises… I'm sure you don't want to see your production farm consuming 99% of the available memory while crawling… So please, plan first. Here's some help for this: Scale search for performance and availability in SharePoint Server 2013 . But you might have some dev or demo environments, for sure, where you cannot have more than one crawl...

A main criterion that distinguishes websites between good and bad usability is the way, how users can enter data to forms.  Imagine a list with around 15 or more fields. Now a user creates an initial item for that he only enters a few metadata to the item like title, description and a date. After that, another user modifies that item and adds some other field-values. And at last but not least, a third user completes the form by entering all missing values. So you want to show specific fields related to users or roles. Wrap that by a workflow with email-notifications if you want but that’s not the topic of my post.  By default, you have a newform.aspx/editform.aspx that displays all those 15 fields which is not quite necessary for the first user. The second user should not see those metadata-fields the first user entered during initial creation and the last user fills the last values. Finally you really want to impress your customer so the fields in ...

Users added to AD group not granted access in SharePoint Clear - SPDistributedCacheItem – ContainerType DistributedLogonTokenCache ELSE: Here’s an interesting scenario I hadn’t experienced before:  SharePoint 2013 farm doing a user profile sync with Active Directory. Security was based on Active Directory security groups managing membership and authorization controlled through SharePoint groups containing the AD groups. As users were added and removed to/from the AD groups, they weren’t seeing the change reflected in the SharePoint sites. After a crash course in claim caching, here’s what we ended up with. First, an admittedly simplistic view of how SharePoint manages tokens: User browses to SharePoint site SharePoint checks local token store (STS) for a non-expired cached claim for that user If not found, STS creates a new claim by querying AD and then adds it to the cache If found, uses the cached claim That covers the user, now lets look at how S...

 Below are listed three different ways to change the URL of an existing list or library. 1. With PowerShell Changing the URL is possible by moving the root folder to a new URL. Here is a PowerShell script to change the URL of an existing library: Add-PSSnapin Microsoft.SharePoint.PowerShell –erroraction SilentlyContinue   $libOriginalUrl = "/Lists/YourLibName1" ; $libNewUrl = "/YourLibName2" ; $web = Get-SPWeb -Identity http://....   $lib = $web .GetList( $web .Url + $listOriginalUrl ) $rootFolder = $lib .RootFolder; $rootFolder .MoveTo( $web .Url + $libNewUrl ) 2. With SharePoint Designer Open the site in SharePoint Designer and in All Files in Site Objects right click the list and click “Rename” to rename it or drag and drop to move it to another folder. For example a list can be moved outside “/Lists” and the Url will change from “webUrl/Lists/List1″ to “webUrl/List1″. 3. With Windows Explor...

Reservation of resources in SharePoint 2013 After migration to SharePoint 2013 I discovered that these features were excluded from the new platform and saved only as backward compatibility. So, you can migrate your application with installed booking calendar from SharePoint 2010 to SharePoint 2013 and you will keep functionality of resource reservation but you cannot activate it on a new SharePoint 2013 application through default interface. Microsoft officially explained these restrictions by unpopularity of the resource reservation feature: http://technet.microsoft.com/en-us/library/ff607742(v=office.15).aspx#section1 First, I found a solution for SharePoint 2013 on-premise. It is possible to display the missing site templates including 'Group Work Site'. Then you just need to create a site based on this template and you will get the calendar of resources. Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\1033\XML, open ...