| | | When creating columns (or site columns), always try and avoid using special characters such as $, &, # and %. For example:
Instead of "Purchase Order #", use "Purchase Order No" or "Purchase Order Number".
The reason is, if you plan using these columns later in code or in SharePoint Designer (for example, the dataview webpart), you will have problems and challenges, and I've seen specifically myself, the 'Send to Row' functionality break, when columns are named with extended characters. | Columns, Web Parts | | | | When creating lists, always create your list without spaces and simply modify the description after the list has been created, to put the spaces back.
Reasons:
1. The URL will be shorter (spaces are changed to %20) so every space adds 3 additional characters
2. The URL will be nicer to look at (see #1, no %20's)
3. If you decide to reference these lists later via SharePoint Designer or .NET, you won't need to deal with thanslating the %20 information in your code, which means you can develop faster
4. It's easy, and takes an extra 10 seconds per list - hardly a big deal, eh? But with a big, long term reward | Lists, Sites | | | | It is easiest to manage permissions at only the site level, whenever possible. This means you should create your site hierarchy in a way that allows you to assign permissions to sites that are appropriate to all securable objects within the site, such as lists, libraries, folders within lists or libraries, documents and items.
Although you can assign unique permissions on any securable object in the site hierarchy, to do so is more cumbersome than inheriting permissions.
As much as possible, arrange sites, subsites, lists and libraries so that they can inherit most permissions. Put sensitive data into separate subsites, lists, libraries, and so on. | Lists, Security, Sites, Site Collections | | | | At a minimum, I create at least one SYSImages Picture library in my root SharePoint Site Collection. You may find, due to permissions, that you will create one in other sites as well, mileage will vary. The Purpose for doing this, is a central (within SharePoint so that you avoid using and depending on outside images) place to put icons and images that you will use on your site for icons, content editor web parts, etc. Call the picture library whatever you like but... 1. Do not show it on the Quick Launch bar (its for you, not for everyone else) 2. Put all system used images in there 3. When referring to the images in that library in your site, BE SURE to use the relative path to the library and not the full URL as you may find in the future (or now), that you will have multiple AAM's (Alternate Access Mappings), a fancy word for saying 'different URL's to point to your site. E.g. FULL URL (don't use): https://portal.itgroove.org/SYSImages/emailicon.jpg RELATIVE URL (do use): /SYSImages/emailicon.jpg | Miscellaneous, Sites, Site Collections, Web Parts | | | | I hear this all the time. Folks are tired of having to repeatedly enter their usernames and passwords, when connecting to their SharePoint site, or opening/saving Word and other documents in SharePoint document libraries. The simple fact is, if this is your YOUR SharePoint site, you should TRUST it. And you tell your browser you TRUST your SharePoint site, by ensuring the IE (Internet Explorer) Security Zone for it is set to the 'Intranet Zone'. This is a positive in two scenarios: Domain/Trusted Windows Workstation - your domain already has a 'trust' with your workstation, therefore IE just 'passes' along your credentials, when the site is in the Intranet Zone Non Trusted Windows Workstation - even in situations where the workstation isn't in the domain, the Intranet Zone has a setting for 'remembering' your username and password for you and will do so. One final/closing note. You need to ensure the Intranet Zone is set to the 'defaults'. Each zone can be manipulated/modified to a different security zone setting but the defaults are the ideal for ensuring SharePoint functions for you, properly. See the PDF we've (itgroove) created below, to help guide you through the simple process of ensuring your Intranet Zone is defined, for your Internet Explorer (IE) browser. In addition, you can have your local IT department define the 'Intranet Zones' for all computers on your network, using 'Group Policies' to address this in one fell swoop. Reference PDF: http://blog.brainlitter.com/sharepoint/SharePointDox/HowTo%20Documents/SharePoint%20Intranet%20Pass%20Through%20Authentication.pdf | Miscellaneous, Security, Sites, Site Collections |
|
|
|