Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Professional SharePoint 2007 Records Management Development: Managing Official Records with Mi
This is the forum to discuss the Wrox book Professional SharePoint 2007 Records Management Development: Managing Official Records with Microsoft Office SharePoint Server 2007 by John Holliday; ISBN: 978-0-470-28762-0
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional SharePoint 2007 Records Management Development: Managing Official Records with Mi section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Display Modes
  #1 (permalink)  
Old August 30th, 2010, 06:25 PM
Registered User
 
Join Date: Aug 2010
Posts: 3
Thanks: 1
Thanked 0 Times in 0 Posts
Default Record Center and content type of the incoming documents

Hello all

I have same content types in both collboration site and record center sites.

When I used Send To command to send a document from collaboration area to record center, all the properties and metadata are promoted to columns in the Record center library. But the Content type of the document in record center is set to "Document" even though the incoming document's metadata has Content type value. Will all the records end up as Document content type if we are using default router?

Thanks
Reply With Quote
  #2 (permalink)  
Old August 30th, 2010, 06:53 PM
Wrox Author
 
Join Date: Jun 2007
Location: Fernandina Beach, FL, USA.
Posts: 10
Thanks: 0
Thanked 2 Times in 2 Posts
Send a message via MSN to jholliday
Default

Quote:
Originally Posted by Kaabee View Post
Hello all

I have same content types in both collboration site and record center sites.

When I used Send To command to send a document from collaboration area to record center, all the properties and metadata are promoted to columns in the Record center library. But the Content type of the document in record center is set to "Document" even though the incoming document's metadata has Content type value. Will all the records end up as Document content type if we are using default router?

Thanks
The content type of the incoming record is used for 2 purposes. First, it is used to select the routing table entry that tells SharePoint where to place the document, which aliases to match, what custom router (if any) to use, etc. After SharePoint determines which document library to place the document into, it then looks at the library to see if there are any columns that match the incoming metadata. Finally, it places the document into the library. If the library does not have content types enabled, or does not have a content type that matches the incoming document, the resulting document will have the default "Document" content type. So, you have to make sure that the target document library also has content types enabled and that the content type has been added to the library.
__________________
John F. Holliday, Author, MOSS MVP
Reply With Quote
The Following User Says Thank You to jholliday For This Useful Post:
Kaabee (August 30th, 2010)
  #3 (permalink)  
Old August 30th, 2010, 09:28 PM
Registered User
 
Join Date: Aug 2010
Posts: 3
Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by jholliday View Post
The content type of the incoming record is used for 2 purposes. First, it is used to select the routing table entry that tells SharePoint where to place the document, which aliases to match, what custom router (if any) to use, etc. After SharePoint determines which document library to place the document into, it then looks at the library to see if there are any columns that match the incoming metadata. Finally, it places the document into the library. If the library does not have content types enabled, or does not have a content type that matches the incoming document, the resulting document will have the default "Document" content type. So, you have to make sure that the target document library also has content types enabled and that the content type has been added to the library.
Hello John
Thanks for your reply. I have your book and it is a great reference in Records management topic.
I have made sure that the record center’s library is allowed to have content types and the same content type is deployed in both collaboration area and record center (via feature).

I have read in the book that metadata promotion in record center is done for only simple data types and it does not work for complex data types like look ups and user information. The properties.xml file has my content type listed in it as string type. But out of box “Send To” still does not set the content type in the destination library and it is always document type.
I have noticed that properties.xml has more than one <ContentType> nodes in it. One of them is string type and another one is lookup type. Not sure why there are 2 <ContentType> elements in the xml file and why string type is not promoted to the record in destination.
Thanks in advance.
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Content-type = text/html tarran C# 3 December 5th, 2004 07:36 AM
How to Keep track of all incoming Documents reddynet Biztalk 0 July 17th, 2003 04:58 AM



All times are GMT -4. The time now is 04:04 PM.


Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.