Hi Dawina, This is not configurable in SBM today. I would suggest adding this idea to the "idea exchange". This is a tab near the top of this page. This will allow others to vote for this idea. As long as you are in the idea section, be sure to look around an vote for other ideas you like too. 

Hi Vickie, thank you for your answer! Too bad to hear that this is not possible. But thanks for the tip about the “Idea exchange” tab, I'll have a look there. 

We thought of one more idea. It's not exactly what you asked for, but it might be helpful.

You could create a report with all the fields that you want, then save it with a name such as "Listing Report Template". Then, when a user needed to create a new report, they could search for "Template" to find the template report. Then, they could edit this report (which would give them the default fields), setup the filters etc, and use "save as" to create their own report.

To prevent users from changing the "template" report, you could save it as a User report (for example) and only give them permissions to "Run User Reports". As long as they don't have "Edit User Reports", they won't be able to change the template.

This can be accomplished with a bit of majic ....

Background:

The "default" fields are those specified in the primary table's "value display format" in Composer.

For example:

In TS_TABLES, the information for the "value display format" is in the TS_FORMAT column and consists of a quoted string with the format followed by the TS_IDs of the fields where the "{0}" in the format string is replaced by the first field (4817 in the pic below).  The "{1}" is replaced by field #4815, etc.

NOTE: I inserted the double SLASH chars just to provide a point of reference when viewing an item.

Here's what that looks like when viewing an item.  Note the double SLASH characters.  I think the TITLE is always include.  Including the Item ID is an option in Composer.

NOTE: The display width above is not enough to show the "Simple Text Field" ... "(None)" is the Owner field.

As it turns out, if there are any additional field TS_IDs listed in the TS_FORMAT column that do not have a corresponding "format tag" like "{0}", "{1}", "{2}" etc, then those fields do appear in the report editors list of "default" fields but they don't appear as part of the item's "value display format".

For example, appending a couple extra field IDs (4861 and 4862) to the TS_FORMAT field in TS_TABLES:

makes those fields show up in the list of default fields in the report editor:

I used SQL to add the 2 additional field IDs to TS_FORMAT then restarted the SBM server.

Caveats:

• OpenText does not entirely condone users modifying things with SQL.
• Make sure you update the TS_FORMAT column in TS_TABLES for the correct table, and only that table.
• Subsequent deployments will revert the values in the TS_FORMAT column back to their original values.
• You break it, you bought it.  ;-)
• Have fun!

Officially, I'll say, don't mess around with the tables in SQL. It will only cause you trouble. 

Unofficially, I'll say. WOW! Send the man a t-shirt. You win the award for the "most creative suggestion" of the year and a second award for "best list of caveats".