BIA Dependency Assessment Columns

Devin the Dude
Kilo Guru
  • I am looking for a way to show more than 6 fields/columns for the BCM Dependency Assessments within the BCM Workspace, has anyone had any success with this?
  • I have not had any success using the grid configurations or list views, even though they are setup correctly (tested and confirmed)

 

DevinValencia3_0-1679276773328.png


One thing that is really interesting, is that the User Preference for bcm.gridCol.<ANY_NAME> seems to show that some fields are set to hidden for some reason:

DevinValencia3_1-1679277076789.png

 



1 ACCEPTED SOLUTION

Devin the Dude
Kilo Guru

The solution I ended up implementing for this required a grid configuration, then the grid configuration columns, then activating the grid configuration and finally setting the system wide user preference as stated in the original column.

 

For each of the columns where hidden: true, just set to hidden:false in the user preference record. this shows the columns that were hidden previously.

 

Word to the wise, the user preference does not get captured in an update set, be sure to manually import or run a fix script when managing the release.

View solution in original post

2 REPLIES 2

Rajesh_Singh
Kilo Sage
Kilo Sage

In ServiceNow, the number of fields displayed on a grid in the workspace is usually limited. However, there's a workaround to display more columns by creating a custom list view with a UI Style. we have done that for one of our project

 

 

If you found my response helpful or applicable, please consider marking it as correct or helpful to assist others who may be seeking the same information.

---------------
Regards,
Rajesh Singh

Devin the Dude
Kilo Guru

The solution I ended up implementing for this required a grid configuration, then the grid configuration columns, then activating the grid configuration and finally setting the system wide user preference as stated in the original column.

 

For each of the columns where hidden: true, just set to hidden:false in the user preference record. this shows the columns that were hidden previously.

 

Word to the wise, the user preference does not get captured in an update set, be sure to manually import or run a fix script when managing the release.