The other day I decided to start a power user best practice series. I started with site columns and now the next logical step is content types. I have found that many times experienced users don’t realise the importance of a properly setup content type. Because of this, they often are recreating the same data, having to redo the content types and in some cases blow them away and start over (both of which are a real pain if the CT is already being used). The intent of this post is to cover the best ways to create your content types.
I was recently hosted by CIPS Saskatchewan to give my Leading Practices for Planning and Implementing a SharePoint Environment presentation. It was a great time and I really enjoyed giving it. I will also be presenting the session in October at the Victoria SharePoint User Group and at SharePoint Saturday Redmond. I have updated the slide deck somewhat so wanted to provide it to everyone for them to download.
Thank you to all the organizations for allowing me to present this session and thank you to everyone who came out and attended. I hope you gained something from the presentation.
Thanks for reading!
Recently I was configuring search to access my SQL Server data via an external content type for a demo I was presenting. Once the content source was configured I ran the full crawl to populate the index with the data from my external source. After about a minute the crawl was marked complete. So naturally I am going to want to test it and make sure my data is pulling through. The external data is a basic asset database so I did a search for one of the manufacturers I knew was in there. Received the dreaded “Nothing here matches your search” message.
Well I know there is data in there so obviously something went wrong. I know what is wrong as I have done this before, but I want to go through some of the troubleshooting steps you can do to help determine the problem.
This weekend I had the privilege of speaking at the SharePoint Saturday Conference in Vancouver. At the conference I spoke on no code solutions for SharePoint Business Connectivity Services and the different features you had access to out of the box. It was a great experience and one I hope to repeat in the future. This presentation seems quite popular as I will be giving it again at the SharePoint Saturday in Calgary and the Prairie Developers Conference in Winnipeg.
As promised for all of these sessions I have attached the slide deck here for you to download for reference.
Thanks for reading.
My apologies to all who have been waiting for this. I was going through my blog site and saw this post had been sitting in draft for quite some time. I had thought I had posted it a long time ago. Guess I hadn’t. My apologies.
So this is a topic I have spoken on a few times. Basically it’s all about using PowerShell to install SharePoint for you. Now there already is a tool out there called AutoSPInstaller which is a great tool now that it has an added feature of a GUI interface to build out the xml config. I would like to think that my scripts are much easier to work with than that. However, in some ways AutoSPInstaller does more than my scripts in the configuration world, but my scripts do something that AutoSPInstaller won’t. They will also build out your entire environment, pages, lists, web parts and all.
I did up this presentation not to show off my code or to give it to others (which I have no problem doing), but I actually did it to show everyone just how easy and slick it is to use scripts to complete your work for you. It also gave me a place to come back and grab bits of code that I could use here and there. The GUI, while I wouldn’t call clunky, is not the smoothest experience. And waiting for pages to refresh or having to redo steps because you clicked something you shouldn’t or filled in some incorrect data is a real pain. This is where scripting comes in. Yes it takes you longer to build the script, but in the end you save time. I have reused these scripts many times now. To give you a comparison, when we deployed these environments, my script configured and built our DEV, TEST and PROD environments (pages, lists, webparts, etc too) in about 30 min for all.
Can your GUI do that for you?