Fields are shown in the Vault Configuration that are used in Vault features that are not active in the affected Vault.

Root Cause:

This is part of the Data Model Harmonization feature that is included in the 18R1 General Release.

Solution:

As of the 18R1 General Release, feature-specific fields are automatically created in Vault, however, they are only functional if the affected Vault feature is enabled on the back end. Only Admin users see these fields unless they are enabled in any document type.

The workaround is to remove the affected fields from all associated document types until the corresponding feature is enabled in the affected vault on the backend.

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 clickinghere.