Meta Data Copy Issue when a document is sent to Records Site

Based on the link below from TechNet,

http://technet2.microsoft.com/Office/en-us/library/884c0583-07e0-4e59-bd0c-dfe2b8229aed1033.mspx

when we send a document from the portal document library to the records center the following action should have occurred with the portal Meta Data

?

The metadata values are copied to matching columns in the destination library in records Center.

But when I check the Meta data values in the destination library none of the matching metadata values are populated .I am not sure if this is a known defect with the records center. We am testing this in our lab which has the RTM edition installed for SharePoint 2007.

The problem is when I view the properties of the destination document in the records center; I don’t see any of the matching Meta data populated. I do see them in the xml file under properties.

Is there some patch that would resolve this issue.

[1742 byte] By [NoelDsouza] at [2008-2-15]
# 1

Does your source library have a content type associated with it? I guess the metadata mapping happens between a content type and records center library.

-Praveen

Pravi4u at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 2
I have content type associated with the source library as well as the destination library but no luck.
NoelDsouza at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 3

Hi,

According to the book MOSS 2007 Administrator Companion ch10:

Although you can configure the document libraries in the Records Repository site with the same Content Types that the source libraries have, the content type association is not carried over to the Records Repository site.

On the other hand, the dialog for filling in missing properties should appear:

Existing document metadata that matches columns in the document library is automatically promoted and stored in the library columns. If there are metadata columns that are not already populated with data, the user is presented with the Missing Properties page to provide the missing values,

I have similar problem. If I create new columns in destination doc library ( that may match or not match the source doc lib columns) , and make them 'required' - when I submitting a new doc with SendTo/Records repository command I get the error that "records repository is not properly configured" .

If I make the destination columns 'optional' - everything works ok, document gets submitted without an error , but I still don't get missing properties dialog.

Thankful in advance fo help,

Marina

Marina at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 4
I finally opened a case with microsoft and showed them the problem.they believe it is a problem with the product.I havent heard back from the support person yet on this case.will post here once I hear back from them.
NoelDsouza at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 5

Hello Noel,

Do you have any news about this issue ?

I tried on several MOSS2007 installations and have always the same problem (no missing properties dialog).

TIA

Jos

JTC at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 6

Jose,

I havent heard back from them yet on this issue.I hope they come back soon else I will be forced to use a custom router to make this happen which I am not in favour off.

Noel

NoelDsouza at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 7

I have the same problem with metadata wich are lookup columns. All the other columntypes are translated back to the corresponding column except for the lookup columns. The lookup column is an lookup on a list with clients. The lookup column is a site column wich is part of a site content type.

I checked the properties xml for any problems and I found out that the record router saves the lookup column as an integer, instead of the name of the client. I think the integer corresponds with the id of the corresponding list item. Does anyone have any information about this problem?

PascalvanDelft at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 8

Hi Neol,

Just wondering if you have got an answer for this problem from Microsoft or if you have a work around solution. I am having the same problem. It's really a show stopper for me, I would really appriciate if anyone could help me out.

Many thanks.

Bing

bbice at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 9

I have seen that this is a problem if you send a document to the recordcenter in another site collection.

The content type guid is not rekognized then

Houlberg at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 10

I received the following email from Microsoft.

we checked the issue with the SharePoint Escalation team and they mentioned that “A Records Repository site is intended to store final copies of corporate records for long-term retention. As such, we've specifically disabled the promotion/demotion of metadata & schema from server to files, because promotion/demotion will break the "authenticity" of the record as submitted. (For example, promotion/demotion of this data into records would break any byte[] based hash features used to verify record authenticity)”.

This feature is on purpose to maintain the fidelity of the files but if you want to change it you can use object model and follow the article:

http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.spweb.parserenabled.aspx as the workaround for the issue.

NoelDsouza at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 11
just want to let you know.this only works with microsoft office documents and not for pdf or any other types of non-office documents.

NoelDsouza at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 12

Hmmm is this link correct?
I think this answer does not have anything to do with this issue.
The record center will show the meta data IF the file comes from the same site collection as the Record Center and the document libbrary in the record center has the same content type attached.

But if the document center comes from another site collection the metadata wil not be shown in the the document library. This must be because the content type guid from the other site collection is not know by the site collection of the record center.

Houlberg at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...
# 13

Where did you find this information ? Logically record center should save metadata for any item it stores , hence the metadata moved and saved via library columns not in the document's own metadata that is (as you are correct about) only available with the Office2007 document format.

regards,

Marina

Marina at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...

SharePoint Products and Technologies

Site Classified