QuickParts can't reference the custom document property

[Michael Nemtsev]

Hello,

I'm using QuickParts and would like to reference the custom document
property inside my Word Document.

But quickPart can see only standard properties as Author, Title and etc, but
not the custom I have.

The question is why the quickPart can't see custom document properties?!
--

 

[Jay Freedman]

Hello,

I'm using QuickParts and would like to reference the custom document
property inside my Word Document.

But quickPart can see only standard properties as Author, Title and etc, but
not the custom I have.

The question is why the quickPart can't see custom document properties?!

The list on the Quick Parts button only shows the built-in properties;
it just wasn't programmed to take account of the custom ones, and you
can't make it do that.

Greg Maxey has an add-in that will help you attach ("map") content
controls to custom document properties. See
http://gregmaxey.mvps.org/Mapped_Content_Control.htm.

 

[Greg Maxey]

Micheal/Jay,

While you can use the Add-In I produce to map contrent controls to xml in
the custom data store, it does not include a feature to map to custom
document properties.

For whatever reason (and I don't know if it is still so in Word2010), MS
choose not to include the custom.xml file that holds custom document
properties in the collection of customXMLParts. A rather lengthy discussion
on this is, and a work around that I proved once is, contained here:

http://groups.google.com/group/micr...p+custom+document+property+to+content+control

 

[Greg Maxey]

Errata,

The discussion linked "does not" show a work around or a method of mapping
CCs to custom document properties. It shows a way to access the cusotm.xml
file that is created in the Open Office XML format file when a custom
document property is created.

Just having acess isn't really good enough. It doesn't make that file a
customXMLpart whereby two way mapping could occur. I suppose with enough
effort you could:

1. Access the file.
2. Create a customXMLpart using its content.
3. Map a CC to that customXMLpart
4. Use the CCAfterUpdate event to replace the custom.xml file with the
content oc the customXMLpart.

That would mimic one way mapping, but nothing there to reflect changes made
to the property value using the dialog.

I just don't see a way and still don't understand why MS doesnt' make the
custom.xml file a part of the customXMLparts collection.