Hot answers tagged

3

Yes, a list item has both an ID (integer: 1, 2, 3...) and a UniqueId (a GUID). You can get the UniqueId of a given item you know the ID of with PowerShell: $web = Get-SPWeb http://<URL> $list = $web.Lists["<ListName>"] $item = $list.GetItemById(<Integer_ID>) $item.UniqueId You can get the same all client-side by requesting the REST ...


2

No, if you create a Custom form, you are breaking the automatic associations where an updated question (or field in the case of standard lists) automatically shows up. You must maintain your custom form any time you make structural changes to your list or it isn't reflected.


2

I think that this could be your solution: Add a User or Group to the SPWebApplication User Policy for all Web Applications in the farm The interesting code should be Get-SPWebApplication http://sharepoint2010 | foreach { $webApp = $_ $policy = $webApp.Policies.Add($userOrGroup, $displayName) $policyRole = ...


1

Have you tried restoring the site from a different web application/farm recently? One of the things I would try is to change the site collection administrator from the central administration or may be using the account admin, which is already working and try to give the access to admin2 again. Let me know what error you get.


1

After my testing I have detected the problem: control.IsIncludePathData = true; When you select from suggestions, control.Text contains something like this: label | GUID| GUID | GUIDSELECTED When you select from picker, control.Text contains: label | GUIDSELECTED So, you can avoid the problem with control.IsIncludePathData = false, or assigning the ...


1

Why do you need a third party tool?! You can migrate the site directly from 2007 to 2010 and then from 2010 to 2013. Read this article.


1

Do I have to call executeQueryAsync twice? Once to get the list items and the 2nd to act on all of them? Yes. Your first query gets the list of items (declare them in the parent scope, obviously, so that they are accessible on the success callback), and in the function of success callback, you can iterate through them to fire individual queries to modify ...


1

You will need to create custom copy of the blog.xsl where you add this to the position where you want the ratings to be shown: <!--Start Blog Post Average Rating --> <div style="margin-left:5px;"> <xsl:for-each select="$Fields"> <xsl:if test="@Name ='AverageRating'"> <xsl:choose> <xsl:when test="@Name='AverageRating'"> ...



Only top voted, non community-wiki answers of a minimum length are eligible