A shared document field is being set to blank in Vault. This change is captured in the Audit Trail. No workflow causes it to be set to blank. The field is not changed to blank by a user. It is not set to blank using an Entry Action. The user cannot determine what is causing the document field to be set to blank.
Disassociate a shared Document Field from the document's Document Type. The next time the document fields are saved on that document, it sets the value of that Document Field to blank.
Making the shared Document Field Inactive rather than disassociating it from its Document Types ensures that the field no longer appears on documents. It also ensures that the field maintains its value (It does not get set to blank on existing documents).
Vault Help Documentation: N/A
Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.