Since the new User Profile Batch Update API is not available on all tenants yet I have been using the “User Profile Bulk Property Updater” from the OfficeDevPnP samples at https://github.com/OfficeDev/PnP/tree/master/Samples/Core.BulkUserProfileUpdater
This bulk updates user profile properties in SharePoint Online through the use of a CSV file.
I am a big fan of Office 365 Developer Patterns and Practices and this sample is so usefull.
Here is the input format for the CSV fil to update your profiles with hiredate and birthday:
UserName,SPS-HireDate,SPS-Birthday
i:0#.f|membership|atestusr03@unclouded.onmicrosoft.com,01/05/1971,12/04/1971
i:0#.f|membership|atestusr01@unclouded.onmicrosoft.com,11/08/1975,11/22/1975
i:0#.f|membership|atestusr02@unclouded.onmicrosoft.com,12/21/2012,07/03/2012
Tags: Office 365 |
Categories: SharePoint Configuration | SharePoint Development
By installing the KB3114503 https://support.microsoft.com/en-us/kb/3114503 all the listview webparts on your SharePoint 2013 server displays this error repeatedly.
“TypeError: Cannot read property ‘replace’ of undefined”
With danish localization it looks like this:
“TypeError: Værdien af egenskaben ‘replace’ kan ikke hentes: Objektet er null eller ikke defineret”
Workaround
Apparently a workaround is this quickfix https://www.reddit.com/r/sysadmin/comments/40tvqn/quickfix_patch_kb3114503_causes_sharepoint_to/ where you modify the view to display the item title colounm (linked to item) instead of (linked to item with edit menu).
Some reports states that a solution is applying January 2016 CU. And that the KB3114503 update is unable to be removed after installation.
So remember to turn off automatic windows update and test any patch/CU before production!
More
To learn more about the vulnerabilities the KB3114503 fixes, see Microsoft Security Bulletin MS16-004.
Note To apply this security update, you must have the release version of Service Pack 1 for Microsoft SharePoint Foundation 2013 installed on the computer.
Sources
Tags: SharePoint 2013, Security Update, SharePoint |
Categories: Technical
All of the available out-of-the-box content types and their related columns in SharePoint Server 2013 are listed here in a post @JKevinParker http://www.jkevinparker.com/2014/02/sharepoint-2013-content-types-and.html
You can also find the xml for most of the built in content types at your SharePoint server under the 15 hive folder TEMPLATE\FEATURES\ctypes\
Here is the PowerShell to fetch all content types on a web
$site = Get-SPSite http://SharePointSite
$web = $site.RootWeb
foreach ($ctype in $web.ContentTypes) {$ctype.Name}
Go here for SharePoint Online content types in Powershell http://social.technet.microsoft.com/wiki/contents/articles/31151.sharepoint-online-content-types-in-powershell-get.aspx
Content Type IDs
Content type IDs uniquely identify the content type and are designed to be recursive. Read more here about the way to construct a valid content type ID: https://msdn.microsoft.com/en-us/library/office/aa543822%28v=office.14%29.aspx
Tags: SharePoint, PowerShell |
Categories: SharePoint Development | Tips and tricks
There is a Nuget library called CredentialManagement that wraps the Windows Credential Management API that supports both the old and the new style of UI http://nuget.org/packages/CredentialManagement/
works perfectly
var cm = new Credential();
cm.Target = "mycredentialname";
if (!cm.Exists())
{
Console.WriteLine("cm is null");
}
cm.Load();
Console.WriteLine("Password: " + cm.Password);
Console.WriteLine("Username: " + cm.Username);
Tags: Credential Management |
Categories: Technical
Following up on a change of default URL for a WebAppllication on SharePoint 2013, the site did not respond correctly.
Finding the a
Unexpected SPAudienceValidator Audience URI '[OLDURL]' is not valid for context
in the ULS led me to this blog post https://gavinmckay.wordpress.com/2014/11/28/fixing-sharepoint-2013-unexpected-spaudiencevalidator-audience-uri-is-not-valid-for-context/
Indeed a caching issue, in my case a flush of the DNS and a reset of the web server was sufficient.
-
ipconfig -flushdns
-
iisreset -noforce
Tags: Debugging, SharePoint 2010, SharePoint 2013, ULS |
Categories: SharePoint Configuration | SharePoint
When using the PowerShell command Mount-SPContentDatabase or adding content database through the Central Admin you will receive this error message:
The SELECT permission was denied on the object 'sysobjects',
database 'mssqlsystemresource', schema 'sys'.
if the SharePoint Admin account has the deny permissions checked. The easy fix was to open SQL Server Management Studio and modify the roles of the admin account on the content database.
- db_denydatareader
- db_denydatawriter
Make sure that db_denydatareader and db_denydatawriter are unchecked on the user.
Thank you Steve! http://stevemannspath.blogspot.dk/2013/03/sharepoint-permission-error-when.html
Tags: SQL Server, SharePoint 2013, PowerShell, SharePoint 2010 |
Categories:
Get the new Roennes.net Blog App at the windows phone store for free and stay up-to-date with new posts on your favorite windows device!
Tags: Windows Phone |
Categories: Windows Phone Development
Got the error while scripting content type modifications with PowerShell and SharePoint 2010.
Error System.Management.Automation.MethodInvocationException: Exception calling
"Update" with "1" argument(s): "The collection cannot be modified." ---> Microso
ft.SharePoint.SPException: The collection cannot be modified.
at Microsoft.SharePoint.SPContentType.Update(Boolean updateChildren, Boolean
ignoreSealedOrReadOnly, Boolean throwOnSealedOrReadOnly, IList`1 exceptions)
at Microsoft.SharePoint.SPContentType.Update(Boolean updateChildren)
at Update(Object , Object[] )
at System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object ta
rget, Object[] arguments, MethodInformation methodInformation, Object[] original
Arguments)
AvailableContentTypes
I was using the AvailableContentTypes[$contentTypeName] to get the content type I wanted to change. But content types retrieved from this collection (as oppose to SPWeb.ContentTypes) are read-only.
$field = $web.Fields[$fieldName]
$cType = $web.AvailableContentTypes[$contentTypeName]
$fLink = new-object Microsoft.SharePoint.SPFieldLink $field
$cType.FieldLinks.Add($fLink)
$cType.Update($true)
The correct way is using the SPWeb.ContentTypes collection as the following code:
$field = $web.Fields[$fieldName]
$cType = $web.ContentTypes[$contentTypeName]
$fLink = new-object Microsoft.SharePoint.SPFieldLink $field
$cType.FieldLinks.Add($fLink)
$cType.Update($true)
Tags: SharePoint 2010, PowerShell |
Categories: SharePoint Development