Wednesday, July 29, 2009

why is the Include-Content button greyed when making a list template?

Apparently this occurs when there is a Lookup-type column in the list. Just remove this column and it should be save-able (sic) with the content. Another optin is to "de-reference" the lookup column. Do this by:

- create a new text column
- go into datasheet mode
- select the entire lookup column and copy/paste into the new text column

The reason this occurs is because a lookup column works by referencing an interal generated name for the list it references.

The "instantiate a template" function cannot recreate the lookup column field (since the referred-to-list may not even exist where the new list is instantiated), so they chose to disable saving the content if this field is present.

Sunday, July 5, 2009

Document conversion not very useful & broken in one case

This is another case where the Publishing parts of MOSS are not integrated cleanly IMO.

I created a site collection under a publishing root level site. This site collection did not have the Publishing Features activated.

When I uploaded a Word 2007 file, the context menu has an item labelled Convert Document >> From Word Document to Web Page.

Not knowing what this was I tried it. You immediately get an error screen displaying:

The site is not valid. The 'Pages' document library is missing.

There is no indication what the problem is related to.

So I created a 'Pages' document library. Tried the same menu item and got the same message.

Then I added the Publishing Infrastructure to my site. Same result.

Then I looked on the web about this error message and I was instructed to check Central Administration. I did this and saw:

Document Conversions Launcher Service is present and started

Finally I made a site collection using the Publishing site template. Then I uploaded the document to this new site collection and tried the menu item again. Lo and behold:

The document converter was able to create HTML from this document, but it had to modify the output:
1 embedded image(s) from the document were not preserved in the HTML.

Click OK to go to the created page.


I went to the page and it looked like Word's old SaveAs Html option. Not very useful!

So this menu item is enabled even though in many instances it will cause an error. Not the A answer!

Regards..

Roger Williams
Franklin Laboratory

copying including associated metadata

There is some good news on this issue.

Basically if you copy a document library item that is a certain content type and contains certain meta-data to another location, using ECB >> Send To >> Other Location, the entire content type will be copied providing that the destination document library has content types enabled as well as the "copied from" content type.

In my tests, if the content type management is not enabled in the docuement library, only the document gets copied and it truncates the metadata. The fact that no message is issued on loss of dat is a bug IMO.

To test this do the following steps:

  • optionally create any needed site columns
  • create a content type (using those columns)
  • create the target document library
  • enable content types (List Settings >> Advanced Settings >> Allow management of content types)
  • include the source content type in the target doclib (List Settings >> Add from existing site content type)
  • save a copy of the target document library URL
  • go to the source document library
  • navigate to the folder or view containing the item to copy
  • use the Edit-Control-Block to perform the copy (ECB >> Send To >> Other Location)
  • paste in the target document library URL (strip off Forms/AllItems.aspx)
  • hit OK twice

This should do it. Note that there are several additional capabilities this should have, including:

  • let the user pick the doclib from a screen
  • let the user select folders
  • let the user select several items to copy simulatneously
  • the system should strip the URL for the user
  • reduce the number of clicks!!

Other needed tests include:

  • content type mis-match but meta-data match (using doclib list columns
  • built-in content types and complete meta-data match

Anyway, at least it works for the center-of-the-street case.

Regards..

Roger Williams
Franklin Laboratory