Several CMDB Workspace Tables have multiple Display Fields, making it random which takes effect - Known Error

Several CMDB Workspace Tables have multiple Display Fields, making it random which takes effect Description CMDB Workspace Tables have multiple Display Fields, making it random which takes effect.

Tables/fields include:

sn_cmdb_ws_ci_additional_attributes CI additional attribute config cmdb_ci_class CI class feature Feature

sn_cmdb_ws_ci_class_config CI class config cmdb_ci_class CI class feature Feature

sn_cmdb_ws_group_metadata CMDB Group Metadata ci_count CI Count group Group

sn_cmdb_ws_ms_data_mismatch_config CMDB Workspace Multisource Data Mismatch Configuration attributes Attributes in comma separated list discovery_sources Discovery sources for data mismatch calculations in comma separated list

sn_cmdb_ws_node_map_profiles Node Map Profiles cmdb_ci_class CMDB CI class layers Layers

sn_cmdb_ws_operational_lifecycle Operational life cycle active Active description Description life_cycle_list Life cycle list name Name

sn_cmdb_ws_service_graph_connector Service Graph Connector app_id Application Id company Company scope Scope

Steps to Reproduce

View the Display fields of CMDB Workspace app tables, grouped by table name: /sys_dictionary_list.do?sysparm_query=sys_package.name%3DCMDB%20Workspace%5Edisplay%3Dtrue%5EGROUPBYname Actual behaviour:

Some will have more than 1 e.g. Table: sn_cmdb_ws_ci_additional_attributes (2) Table: sn_cmdb_ws_ci_class_config (2) Table: sn_cmdb_ws_group_metadata (2) Table: sn_cmdb_ws_ms_data_mismatch_config (2) Table: sn_cmdb_ws_node_map_profiles (2) Table: sn_cmdb_ws_operational_lifecycle (4) Table: sn_cmdb_ws_service_graph_connector (3)

Expected behaviour:

There should only be 1 (or 0) fields marked as display_field=true per table. https://www.servicenow.com/docs/csh?topicname=t_SelectTheDisplayValue.html&version=latest "Only one field can be defined as the display value for a table."

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.