cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Document types should include the option to set default columns just like queries

0 Kudos

Document types should include the option to set default columns just like queries

On queries we can define the columns to use by default from the definition of each query. In a document there doesn't seem to be any such option and we have to configure the document view columns in the viewset that we provide for our users. This is especially problematic because we have staged servers with different field IDs, so we need to be careful what server we connect to when updating the viewset. And because its a mandatory viewset that means just changing the default columns for a document would override everyone's existing viewsets. It would be much simpler from a maintenance standpoint if this could be controlled from type configuration.

 

This is especially a problem for us at Cummins because we no longer use the default "Text" FVA field which is on the Requirement type. We've wrapped our own implementation over it with new fields, which means that FVA field which shows by default in the document view is non-functional to our users. So we can't leave any document view columns as default.

 

As a side note, it would also be nice to control default column width from the field definition.