After reading this blog of Matthias Einig about using Azure Analytics for your Office 365 portal. I tried this on an clients SharePoint 2013 farm. But I didn’t want to create an app to deploy the JavaScript so I created an Console app to deploy this to the specific site collection.
I first wanted to create a PowerShell script, but that does not work with our farm because of the discovering of the ADFS settings.
The last few of weeks I got a requests to create list views that where a bit nicer than the default views. Some requests were to display a certain text as a hyperlink or hyperlinks to display as a certain image, but I also got the request to make a view that did not look like a list view anymore. My colleague jumped on this to create a custom webpart to display this.
I was triggered to write this blog because of a question on Facebook about changing the title of a content type in the content type hub.
I was able to answer this question because I found the same issue a while ago when I was working with the same thing.
The question was: When I create a content type in the content type hub and publish it, the content type is pushed down to all site collections and there you can use it in your lists and libraries.
Within SharePoint it is by default possible to open a list form in a dialog by just changing 1 setting on that particular list. This can be done by going to the settings of the list and choose for ‘Advanced settings’. Here you find the option ‘Dialogs’ where you can change this. This is nice but sometimes you want that new form or some other page also in a dialog. That can be done with a little bit of JavaScript on the page where you want it.
?A few weeks ago I was asked to create a solution to copy a document in SharePoint to another system. This other system had the ability to receive documents and their metadata thru webservices. We have a policy that we only use Out-of-the-box solutions or the app model.
I knew that SharePoint 2013 Workflow no has the option to use webservices so I thought this is going to be an easy one.
At one customer we have a SharePoint 2013 environment with ADFS 3.0 as the main authentication provider. I wanted to create a SharePoint Provider hosted app to do a Proof of Concept. I had configured everything to get started with apps and build a SharePoint hosted app to prove that my settings on SharePoint are correct.
I did the SharePoint configuration with the help of the following 2 blogs: Mirjan van Olst and Wictor Wilén These 2 blogs provided the information and settings that we need to get SharePoint hosted apps to work.
Today I got the question to change the default title of SharePoint at the top of the page They wanted this default text “SharePoint” to be the title of the site they are. This text is inside a delegate control called “SuiteBarBrandingDelegate”. Now we can create a delegate control that changes the text and install this as a solution to our farm. But we have the goal to have as less as possible solutions to our farm.
Last week we upgraded our test environment with SP1 of SharePoint 2013. After some testing we found that publishing of a Content Type went wrong with the following error.
With a quick search on the Correlation ID with PowerShell Merge-SPLogFile-PathC:\proxylog.log-Correlatione9a8929c-5756-20e8-2a9f-e38b648bc237
We found the following message
Failed to get term store for proxy ‘Managed Metadata Service Application Proxy’. Exception: System.Security.SecurityException: Requested registry access is not allowed.
So the Managed Metadata Service has not enough rights in the registry, this can be solved to manually add the correct rights for the accounts “WSS_Admin_WPG” and “WSS_WPG” to the registry key “HKLM\Software\Microsoft\office Server\15.
This week we had an issue where we had some differences in the Content Types that where pushed from the Content Type hub. We wanted to make sure all Content Types where updated in the next push. After some digging around on the internet I found that there is a property in the SPWeb.Properties called “MetadataTimeStamp”. This property contains the date of the last sync with this site collection. If you clear the value of this property, the Content Type synchronization Job will update this sitecollection.
Today I did a presentation at Portiva’s SharePoint & Sushi about PowerShell for IT Pro. In this presentation I told the public about PowerShell en how the IT Pro can use this in his daily work. The presentation is in Dutch.
20140429 - PowerShell for IT Pro—Arjan Cornelissen