Sharepoint applied

______________________________________________________________________________
This blog has been discontinued. Please visit my new site based on a completely different concept:
Sharepoint Resource Center

______________________________________________________________________________

So Office 2007 SP2 is being released today. Surprisingly, there is really not too thorough information out there. Even the MVPs who are normally the first to get a details about new updates and releases seem to be very quiet.

Well, let’s wait and see. In the meantime below is a list of SPD and WSS issues fixed in SP2.

Sharepoint Designer:

• After you back up a SharePoint Server site that spans multiple CMP files by using SharePoint Designer, you cannot restore the Web site.
• Custom list forms do not support attachments.
• Editing a page that contains Web parts that participate in Web part connections causes the connections to be broken.
• SharePoint Designer does not support connecting to SharePoint sites using forms-based authentication.
• The workflow does not start and you receive no notifications when a declarative workflow tries to run as the system account.
• When a data view participates in a Web part connection, paging does not work as expected.
• When a workflow changes a list item and is set to trigger when items are changed in the list, the workflow continues to trigger itself indefinitely.
• When you configure data views by using the on-object property panel in Chinese (Hong Kong), certain strings incorrectly appear in English.
  When you delete the primary list form Web part for a list, you receive no warning that the list may break.
• When you look up an empty string within a declarative workflow, question marks are erroneously displayed.
• When you post back data from an ASP.NET control in a data form Web part, the data form does not remember the state of the parameters.
• When you post back data from an ASP.NET control, SharePoint Designer uses the wrong parameter value.
• When you restore a SharePoint site from an STP site template, data views are broken because of errors in the GUID.
• When you use a data form against a SharePoint Server list that uses lookup fields, SharePoint Server does not submit the form correctly if the lookup source has 20 or more values.
• When you use a data form against a SQL Server data source, SQL Server ignores empty text values when you submit the form.
• You are not advised of any potential upgrade issues with your current SharePoint site configuration.
• You cannot successfully configure a Web part connection that contains a SharePoint Server filtering Web part.

Windows Sharepoint Services 3.0

• Site administrators can create policies on their site content types and can expire items using that content type. If a policy was set on any content type in a site, that policy can no longer be set on content types in the subsites of that site.
• Migrating data may encounter errors when uniquely secured folders contain draft items.
• You cannot use SOAP calls to restore a site that is two levels deep (/1/2/) if the first level does not exist (/1/).
• Search may not work correctly if some document properties contain high value surrogate Unicode characters.
• Calling the WebUrlFromPageUrl SOAP method may not work correctly on Web applications that have certain explicit inclusions.
• SharePoint does not allow some field names to be changed to their original values.
• Confusing errors may be displayed after a database is marked as read-only.
• A comment field is not available for posts on new sites that were created from a saved Blog site template.
• The mergecontentdbs command for STSAdm.exe will not work if the command is executed by a user who is not a site collection administrator.
• Users are not warned when their files exceed the maximum path.
• Pages may display errors when served from 64-bit servers.
• Large files may be changed unexpectedly after the files are checked out and then checked in.
• After a site reaches its quota, the site becomes inaccessible.
• List views fail when they are grouped by calculated fields or by lookups to calculated fields.
• Alerts may not be sent correctly on certain installation languages.
• Survey summaries might not be displayed correctly.
• Breaking permission inheritance may take a long time.
• Importing a site fails when the site that is being imported contains a subsite that has features that are activated.
• Sending e-mail for blog posts might not work correctly.
• Some Japanese content is translated incorrectly.
• Indexed columns may not be indexed after a view is deleted.
• The SharePoint timer service may stop working on 64-bit servers.
• SharePoint uses more memory than necessary for some operations.
• 32-bit systems may perform badly in low memory conditions.
• The operation fails when you try to import a site that has a workflow that is running on uniquely secured items.
• Invitation e-mail messages have broken links.
• Search may not work correctly in certain languages.
• Changing the usage log directory may prevent additional logs from being created.
• Survey questions do not display new lines correctly.
• List view Web parts that use groups do not page correctly when they are filtered by another Web part.
• A search may attempt to crawl sites that were removed.
• When a user selects [today] from the Modified field in a document library view, the following error message is displayed: “Filter value is not in a supported date format.” This issue is fixed in SP2.
• When a user selects [today] or [me] from the Modified field in a document library view, the following error message is displayed: “Filter value is not in a supported date format.” This issue is fixed in SP2.
• When a user selects [today] from the Modified field in a document library view, the following error message is displayed: “Filter value is not in a supported date format.” This issue is fixed in SP2.

A few interesting bits – I’ve highlighted the issues I’ve experienced myself – e.g. “When a workflow changes a list item and is set to trigger when items are changed in the list, the workflow continues to trigger itself indefinitely.” Waiting to see how it’s implemented – detection of workflow loop conditions would be really good.

Filed under: Uncategorized