Database view label not working as expected when importing from XMLIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Description When database views are created, a sys_db_view record is created but there is also a sys_documentation record created for the underlying view. Sys_documentation records are used when the name of a table is referenced throughout the instance. Depending on where the table is being referenced, if the sys_documentation record is missing, users can experience unexpected behavior. Users can find this behavior confusing when they are searching for an affected database view in a filter. Additionally, in order for the imported database view to work important to remember to import the corresponding sys_db_view_table records. These records record the underlying relationships between the tables specified in the database view. Procedure Users can import the sys_documentation records from the instance from which these database views were created. If these records are unavailable for some reason, they can be recreated by following the steps below: 1. Navigate to https://<instance-name>.service-now.com/sys_documentation.do 2. Fill in the table with the 'Table' field with the name from the corresponding database view3. Fill in the Label and Plural exactly as they are configured on the corresponding database view Applicable Versions All currently supported releases Additional Information Without the corresponding documentation record: With the corresponding documentation record: