Wednesday, November 7, 2012

SharePoint 2010 Stretched Farm

Very good information.
 
Killing two birds with one stone: SharePoint HA and DR with stretch farm, and everything you want to know about it

Setting-up SharePoint 2010 stretched farm

It looks like that SharePoint 2013 does not support stretched farm, see http://technet.microsoft.com/en-us/library/cc262485%28v=office.15%29.aspx#hwLocServers
All servers that belong to a server farm, including database servers, must physically reside in the same datacenter. Redundancy and failover between closely located data centers that are configured as a single farm ("stretched farm”) is not supported in SharePoint 2013. 

But as this the comments from this blog shows, it depends and it is often case by case.

 

 

Tuesday, November 6, 2012

Using the Row ID value in a calculated column quirk


Sharepoint has a quirk where it drops the [ ] around ID in the calculated value. This happens when either a new item is added to the list or I edit an existing item. The short-term fix is that every time a change is made, I have to manually go enter the brackets back around  ID but it’s hard to keep up with. Long-term fix is to use SharePoint Designer workflow.

Please see detail here.

Wednesday, October 24, 2012

How to print a single list item in SharePoint 2010

The following is copied from

Derek Halstead's SharePoint 2007/2010 Blog

  1. Open a List
  2. Hit the List tab
  3. Click the Form Web Parts dropdownlist
  4. Choose “Default Display Form”
  5. At the top of the Page – Insert Tab, Click the Web Part button to add a new Content Editor web part (CEWP).
  6. From Categories choose “Media and Content” > “Content Editor” and add it to the main section of the page.
  7. Click the “Click here to add content” and then click the HTML button in the Ribbon to bring up the Edit source code window.
  8. In the window add the following code to display a Print Button at the top of the list item window.

<input onclick="window.print();return false;" type="button" value=" Print this page " />



  • Ignore any warnings.

  • Next, hit the Page tab at the top of the page to view the List item. You should see the Print button.

  • Hit the Print button to print just the list item.

  •  

    Friday, October 12, 2012

    Update-SPSolution limitations

    According to TechNet, The Update-SPSolution cmdlet upgrades a deployed SharePoint solution in the farm. Use this cmdlet only if a new solution contains the same set of files and features as the deployed solution. If files and features are different, the solution must be retracted and redeployed by using the Uninstall-SPSolution and Install-SPSolution cmdlets, respectively.

    How to rename the automatically generated task form in SharePoint Designer workflow



    In SharePoint Designer click on All Files in the Site Objects. In the All Files tab navigate to Workflows and click on your workflow. You should see the xoml file, the rules file, the xsn forms and a wfconfig xml file.

    To rename the xsn form, update the wfconfig xml file. Replace the old name with the new one. That xml file contains the content type related to that task, so you can also change the contenttype name as the 'WorkflowForm' name. After saving the wfconfig xml file you need to restart SharePoint designer and you should see your form with the new name.

    You need to be the site administrator in order to see the All Files link un Site Objects. 

    Also it looks like that Lookup type does not work in Task Form Fields, i.e., you can't have lookup type field in task form. If you do, you may see "SharePoint Designer encountered an error generating the task form" error message.

    Thursday, October 11, 2012

    SharePoint Designer Workflows Process Identity

    When a SharePoint Designer (SPD) workflow runs, it runs in the context of the workflow initiator. This is important to know if the initiator may not have permissions to everything that the workflow does.

    See SharePoint Designer Workflows – what user identity?

    SharePoint Designer 2010 introduces the new impersonation step. Please note that the impersonation step can be run only as the user who authors the workflow. The author of the workflow, most likely, is not the same as the identity of the SharePoint timer job.