Overview:
A Vault field is not displaying the correct date on an object record.
Root Cause:
The affected field is a Date field.
Solution:
Vault Date fields do not take time zones into account when they are created and stored on the back end. This can cause the value in the affected field to display the previous day's date or the next day's date, depending on the time zone of the user that is logged into Vault.
The solution is to create the affected field as a DateTime field, instead of a Date field, so that time zones can be taken into account when displaying the value of this field in Vault.
Related Documentation:
Vault Field Documentation: Vault Date & Time Formats
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.