Using the Merge Fields, you can trigger Vault to search within a Microsoft Word (DOCX only) or Microsoft Excel (XLSX) source file and replace certain tokens with field values from the Vault document. Merging fields can make it easy to create templates that auto-populate with details like product name, document status, and version date. You can also use this to add a title page to a document that shows the document name or document number from the Vault.

How to Add Vault Fields to a DOCX or XLSX File

Vault looks within the uploaded file for text that matches this pattern:

${vault:fieldname__v}

Tokens

Shared

Name ${vault:name__v}
Additional Information ${vault:title__v}
Document Number ${vault:document_number__v}
Type ${vault:type__v}
Subtype ${vault:subtype__v}
Document Category ${vault:reference_model_subcategory__c}
Status ${vault:status__v}
Version ${vault:major_version_number__v}.${vault:minor_version_number__v}
Lifecycle ${vault:lifecycle__v}
Owning Facility ${vault:owning_facility__c}
Owning Department ${vault:owning_department__v}
Product ${vault:product__v}
Document Supplier ${vault:document_supplier1__c}
Training Impact ${vault:training_impact__v}
Superseded Date ${vault:superseded_Date__c}

Initial to Final

Final Date ${vault:final_date__c}

Draft to Approved

Approved Date ${vault:approved_date__c}
Obsolete Date ${vault:obsolete_date__c}

Draft to Effective

Approved Date ${vault:approved_date__c}
Proposed Effective Date ${vault:proposed_effective_date__c}
Effective Date ${vault:effective_date__v}
Obsolescence Approved? ${vault:obsolescence_approved__c}
Proposed Obsolescence Date ${vault:proposed_obsolescence_date__c}
Obsolete Date ${vault:obsolete_date__c}
Periodic Review Frequency ${vault:periodic_review_frequency1__c}
Last Periodic Review Date ${vault:last_periodic_review_date1__c}
Last Periodic Review Decision ${vault:last_periodic_review_decision__c}
Next Periodic Review Date ${vault:next_periodic_review_date1__c}
Start Periodic Review Date ${vault:start_periodic_review_date1__c}