Tuesday, 30 July 2013

Access vs InfoPath etc


·         Use SharePoint lists for simple applications with not toooo many columns
·         Use InfoPath web forms if you’re creating a lot of columns of the type ‘Multiple Lines’…
·         Use Excel Web Apps, if you’re licensed, if you are trying to make a list behave just like a spreadsheet. You know you’re going to need Freeze Panes at some point…
·         Use Access Services if you’re creating a lot of columns, need more functions to calculate, more queries to filter and more items to view than a list can possibly handle… and you’re on a budget that excludes more expensive alternatives

thanks to Sharon Richardson for this - only put it on here for my own reference

useful ps1 for iterating stsadm

[System.Reflection.Assembly]::Load(“Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”)
$WA = "http://moss.litwareinc.com"
$webapp = [Microsoft.SharePoint.Administration.SPWebApplication]::Lookup("$WA")
foreach($site in $webapp.sites)
{
$url = $site.url
write-host $url
stsadm.exe -o gl-propagatecontenttype -url $url -contenttype Document >C:\output.txt 2>&1
}

STSADM can't find site URL

Apostrophes don’t show in site URLs:

e.g.

/sites/COO/Customer Services/Property, Change, Customer Op's – shows in browser

/sites/COO/Customer Services/Property, Change, Customer Ops – works in STSADM and shows in Enunumallwebs

SharePoint Information Architecture Diagram

Here is the template I use for Information Architecture designs. It's built using Mindjet and I flesh the nodes out with the low level d...