Skip to main content
hamburger menu Created with Sketch.
We are currently experiencing an issue with creating new support tickets from the Help Center portal. Some users are unable to select the appropriate form when submitting their tickets. We are working to resolve the issue.

Search the Knowledge Base

Why Do Standard and Custom Yes/No Document Fields Default Differently When the Value is Blank in Vault?

  • Updated

Question:

Yes/No field stores a true or false value and this is also called a boolean field.

  • If a Standard Yes/No document field is blank, the value defaults to No.
  • If a Custom Yes/No document field is blank, the value defaults to blank.

Example

  • CLM Content is a standard field and the value is blank.

    mceclip1.png


  • Contractor? is a custom field and the value is blank.

    mceclip2.png

In the report, the CLM Content shows a value of No, but Contractor? appears blank.

image-2022-01-27-11-31-11-961.png

 

Why do the standard and custom Yes/No document fields behave differently?

Answer:

This is working as expected.

  • For a standard Yes/No document field, the default value is No. 
  • For a custom Yes/No field, there is an option for admins to set the default value (Navigate to: Admin --> Configuration --> Document Fields).

    If the default value is not set, it defaults to blank.
    If the default value is set to No, it defaults to No.

mceclip0.png

Related Documentation:

Vault Help Documentation: About Document Field Administration   

Powered by Zendesk