From my last PowerShell Article “PowerShell from an Array to Comma Separated file (CSV) via the PSObject“, http://goo.gl/3ATJgp, I pointed out that a CSV or Comma Separated Value file is kind of like a Hash Table where every value is associated with a column heading. In PowerShell, just because you get somewhere is no guarantee you
Let’s begin by taking a look at the “managed metadata navigation” feature. One of the big challenges to navigation inside SharePoint is that it needs to be set up in each site. This causes a problem if any of the links are removed because then I need to go in each site and delete or update the links
As usual, when I embark on a PowerShell project it’s always a learning curve. One might think with all PowerShell’s flexibility, you could just use PowerShell’s” export-csv” command with an array and be on your merry way. It never turns out to be that easy. While working on a PowerShell script for SharePoint 2013 to
1. Error: Unable to properly communicate workflow service. Resolution : Re-installed workflow manager by removing FQDN(servername.domainname) with Service Bus 1.0 cumulative update 1. Do not use FQDN (fully qualified domain name). Ex: SP2013DEV01.Contoso.com à SP2013DEV01\SP2013DEV01 Reference: For Install and Uninstall Workflow Manager http://technet.microsoft.com/en-us/library/jj193448 2. Error : Create designer WF for testing. When you trying to publishing
Document Sets are awesome! During my assignment at an asset manager in the Netherlands, I really started to appreciate the power of Document Sets in SharePoint. I never really was a big fan (not sure why exactly) and never used them. One of my colleagues from the Intranet Team showed me the benefits and now
In Office 365 / SharePoint online, a publishing page with a list of views pointing to a different list can be provisioned using a feature containing a File element containing a view. Example: <?xml version=”1.0″ encoding=”utf-8″?> <Elements xmlns=”http://schemas.microsoft.com/sharepoint/”> <Module Name=”ModuleName” Url=”$Resources:cmscore,List_Pages_UrlName;”> <File Url=”default.aspx” Type=”GhostableInLibrary” Path=”ModuleName\default.aspx” IgnoreIfAlreadyExists=”TRUE” > <Property Name=”Title” Value=”Home” /> <Property Name=”IncludeInGlobalNavigation” Value=”FALSE” />
I know there are a ton of tools out there for moving content within SharePoint. Heck, SharePoint itself even kind of gives you some tools of it’s own. Presented here is MY quick and dirty way of moving documents from one location to another while retaining the Modified, Modified By, Created By, and Created fields.
When I first heard about Managed Metadata Navigation, I thought all of my navigation dreams had come true. Alas, it didn’t quite work as expected and the limitation of a single site collection use really had me chapped. In all of the dark corners of the Internet that I was looking for a solution to
So, I’m no developer by heart, and by trade I wouldn’t say I had a strong desire for it either, but I have my moments of brilliance. Then there are times when I run into something with SharePoint that truly makes me wonder about my life, but for the most part I’m content with bending
As of now, Visual Studio 2012 supports only BCS model with OData (Open Data Protocol) Services for Apps for SharePoint. So let us see what this OData and how to create an “External Content Type” using Visual Studio 2012 for SharePoint 2013 Online. What is OData? The Open Data Protocol (OData) is a Web protocol
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]
