How to Reuse Custom Word Document Properties Across Files
Question details
The user wants to know how to share, link, or reuse custom document properties across multiple Word documents.
- Product
- Word Processing
- Device & OS
- not provided
- Scenario
- Creating standardized templates or a suite of documents that require the same custom metadata, variables, or text elements.
- Observed behavior
- Custom Word document properties are inherently document-specific and do not automatically sync or share across different files.
Determine whether your primary goal is to reuse text snippets or to centralize background metadata, as different objectives require different features like Quick Parts, Mail Merge, or macros.
Use an Excel Workbook with Mail Merge
By storing your shared custom properties in a centralized Excel workbook, you can map them across multiple Word documents using the Mail Merge feature.
Since document properties are strictly tied to individual files, a database approach is often the most reliable method for sharing data. An Excel workbook acts as your single source of truth for properties.
Open Excel and create a new spreadsheet. Use the first row for headers representing your custom properties (e.g., ProjectName, ClientName) and fill the row below with the corresponding values. Save the file.
Open your Word document, go to the 'Mailings' tab, click 'Select Recipients', and choose 'Use an Existing List'. Locate and open your newly created Excel file.
Click 'Insert Merge Field' on the Mailings ribbon and place your custom property fields wherever they are needed in the document.
Click 'Preview Results' to ensure the properties load correctly, then click 'Finish & Merge' to generate the final document.
Utilize Building Blocks for Reusable Content
If your custom properties are actually blocks of standardized text or fields, save them as Building Blocks (Quick Parts) to reuse them across any document.
Use Document Variables in a Global Template via Macros
Advanced users can use VBA macros to store document variables within a global template, making them accessible to any file that attaches the template.
Create and Manage Standardized Documents in WPS Office
WPS Writer offers seamless support for templates, custom properties, and Mail Merge, allowing you to effortlessly centralize and reuse data across multiple documents.
- 1. Open WPS Writer: Launch WPS Office and create a new Writer document or open your existing template.
- 2. Access Mail Merge: Navigate to the 'References' or 'Mailings' tab on the top ribbon to access the built-in Mail Merge toolkit.
- 3. Connect Data Source: Click 'Open Data Source' to connect your centralized Excel workbook that holds all your shared custom properties.
- 4. Insert Fields and Merge: Use 'Insert Merge Field' to place the properties in your text, then select 'Merge to New Document' to populate them automatically.
Frequently Asked Questions
Where are custom document properties saved?
Custom document properties are embedded directly within the individual document file's metadata. They are not stored in the application's central settings or registry, which is why they do not automatically sync across separate files.
Can I copy custom properties from one document to another?
While there is no native drag-and-drop feature to copy custom properties, you can use VBA macros to script the transfer of custom properties from a source document to a target document. Alternatively, saving a document as a template (.dotx) retains its custom properties for any new file generated from it.
What is the difference between custom properties and document variables?
Custom properties are visible and editable in the document's Info or Properties panel, making them accessible to standard users. Document variables are hidden in the document's background and are typically only created, modified, or read via VBA macros or DOCVARIABLE fields.
Why aren't my Building Blocks appearing in other documents?
If your Building Blocks or Quick Parts are missing, they were likely saved to the current document's specific template rather than a global template like 'Normal.dotm'. To make them available everywhere, ensure you select a globally loaded template in the 'Save in' dropdown when creating the Building Block.
