Problems with Office files and mapping

[mark.cloyed]

Has anyone else run into problems with mapping between vault properties and Office documents?  I have started a new vault from scratch and tried both using and not using the manufacturing template in Vault Professional 2018.2.  Some property mappings are OOTB, like title and subject.  Some are newly created and mapped to custom properties in the DOCX.  Upon check in, none of them are being read into the vault properties.  All mappings are set to bi-directional, and I have removed the office add-in and reinstalled it.  Has anyone else experienced this, or has someone got it working?

Thanks,

Mark

[mark.cloyed]

A quick update: I can push values from the vault properties to the file, but cannot read properties from the file into the vault properties.  All properties are set to bi-directional.

[Jason.Courtemanche]

Hi @mark.cloyed,

What properties are you trying to map? The Title and Author properties mapped bi-directional. On check in the data from the Word doc updated the Vault Properties. I was able to edit the title in Vault and have it update in the Word doc.

I also tested by mapping word count (Set as one direction: FIle > Vault) and was able to get the data from the drawing to go into the Vault properties.

Ideally, I want to try testing with the same properties you are testing with. Can you send me a sample word file? I will install the same update and test again.

Regards,

Jason

[mark.cloyed]

Hi Jason,

Thanks for the reply.  This is a sample doc.  I was trying to use the standard properties of Title and Subject, as well as two custom properties, Client and Site.  I used the existing mapping for Title and Subject, and created my own bi-directional for Client and Site.  So far, my experience is nothing comes from the file to the vault upon check in, but I can push values from vault to the file.  Again, I am unsure if it is my vault, since I tried two fresh ones, but wanted to make sure it isn't a problem with vault or one of the updates.  This worked fine in previous versions.

[smilinger]

Try to add the AutodeskVault user to the Administrators group on the server. I have experienced this problem and solved it like this.

Looking at the server logs you can see some error information about failed to read properties etc, however, .doc or .xls files (2003 format) doesn't have this problem.

[Jason.Courtemanche]

Hi Mark,

Thank you for the sample file. I was not able to reproduce the same issue. Please send me a private message and we can figure out a time to do a screen share and look at this.

I test this issue with your file once with Administrator and as a Vault User (Doc Consumer, Doc Editor Lev1, Doc Manager Lev1). Both users had no issue. 

Tested with:

Windows 10

Vault 2018 2018.2 Update

Microsoft Work 2016 MSO (16.0.8431.2110) 36bit

Regards,

Jason

[Jason.Courtemanche · Accepted solution]

Hi @mark.cloyed,

It was nice talking with you. I would try installing the latest update for Word so its the same level as mine.

As a workaround, the mapping will work if you use a .doc instead of .docx or install Word updates. 

Regards,

Jason