In SharePoint 2010 WIKI page infrastructure, you get to modify the WIKI page in a standard free-text format.
The WIKI page is a list item in the WIKI page library. As every list item, WIKI pages can have custom fields, both content type inherited and specific library fields.
While writing this post, I discover an issue while migrating blog content to SharePoint Online. The issue was pictures associated with blog posts published using Live Writer (and so stored as attachments on SharePoint) were not migrated. This issue is not really a product bug as this way of blog posting is using specific SharePoint API’s. I’m really impressed by the quality and the responsiveness of AvePoint Support team. Only a week was needed to have confirmation of repro, details about the issue and get a fix. Whaou!!!
I’ve seen plenty of technical mistakes when implementing SharePoint, particularly in larger environments when the risks of failure are higher. Here’s a countdown of my top ten “favorite” SharePoint mistakes:
With the release of SQL 2012, Reporting Services got a remake specifically for SharePoint 2010. Reporting Services can now be configured as a service application specifically to allow for scaling within your infrastructure. To enable this in SharePoint you must first have installed the SharePoint component from SQL 2012. You can find this by running the installer for SQL and selecting the following:
