Originally Posted by jholliday
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.
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.