In those documents, make any content controls linked to the data non-updatable. Use that XML to create the CustomXMLPart in each document where you need to share the values. Ensure that your XML structure has single child element within the Document element, e.g.You get some cheap documentation of the values, and updates could in theory trigger copying of the data to other documents sharing the values. In the latter case I would create a single Word document with an updateable content control linked to to each item in the Part. Depending on who or what is maintaining it, you could make the "master" either a standalone XML document, or a Word document with a custom XML part.Decide that it should be read-only data except in the "master" copy of the XML.Define your common data and an XML structure to house it.If content controls and the fact that Word does automatic propagation of values are what you want, personally I would probably do things this way: Nor can you map a content control to a custom XML part in another document (as far as I know). These days I would avoid LINK fields because they often spell trouble. If any of your users are on Mac, INCLUDETEXT fields are probably the only way to go, and even they will cause difficulties because of the different path and file naming conventions.ĪFAIK there is no facility to link content controls to content controls in other documents except via LINK fields or INCLUDETEXT fields. You don't say how you are using your content controls or whether you want users to be able to update their values via any of the documents, or only through the "shared" document. Should be a comment, really, but too long.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |