One of the restrictions and limitations in MOSS 2007 page layouts was that we could not easily change the page layout for a page unless we opened SharePoint Designer 2007. We'll see how we can do it easily in SharePoint 2010 with SharePoint Designer 2010.
You've got people putting their documents into SharePoint, and assigning metadata tags. They appreciate that they can now find the documents they want more easily, using views grouped by client or consultant, instead of digging through folders. But where's the "wow factor": something that makes them really sit up and notice how much better things are with SharePoint? Something that makes all the "tagging" hassle worthwhile?
SharePoint Sites can be edited using SharePoint Designer for customizing the user interface and other purposes. But at times, it could potentially affect the performance of sites. In such cases, some administrators prefer to not to allow customization using SharePoint Designer.
The SharePoint 2010 Business Data Connectivity Service allows connecting with external data systems (WCF service, database, .Net assemblies). This is an improved version of the Business Data Catalog in SharePoint 2007. But you can get an error...
"Business Data Connectivity metadata store is currently unavailable"
...when navigating to the External Content Types using SharePoint Designer 2010.
One of the restrictions and limitations of SharePoint Designer 2007 was that we can't save our scripts to be reusable for the entire site. But with SharePoint Designer 2010 we'll see how to create a reusable - code/script snippet.
SharePoint 2007 enabled the ability to read external LOB (Line Of Business) systems like SQL Server, Web services or .Net Assemblies, but in SharePoint 2010 we'll see how to create full CRUD (Create - Read - Update & Delete) operations.
Creating efficient SharePoint Designer Workflow emails can be tricky. There are a couple of salient points you need to know in order to leverage this to its full extent. In this article we will discuss these points.
I would like to be able to centralize a message and be able to roll it out to multiple SharePoint sites simultaneously. When the message changes, I only want to edit one section and have the changes roll out everywhere automatically.