How to enable a custom field to be available in reporting as a Group by

Adam Robbins1
Mega Guru

Hi,

I am wondering if anything special is needed to enable a custom field to be available as a Group by in reporting.

I created 2 custom fields on the Incident table.  1 that concatenates the Category and Subcategory and another that concatenates 2 other custom fields for a Cause category and Cause subcategory.  The first one is available as a Group by while the 2nd one is not.

Here are some screenshots:

Custom field that is available as a Group by:

find_real_file.png

Custom field that is NOT available as a Group by

find_real_file.png

Thanks,

Adam Robbins

 

CORRECT ANSWER: (ServiceNow does not allow me to mark my own reply as a correct answer, so I'm pasting it here)

I got it working now.  I went back into the Dictionary and temporarily adjusted the Type from String to Choice and then Saved.  Then I adjusted back to String and saved again.  Now it has the Group by option.  I am not sure why that worked though.

Thank you,

Adam Robbins

1 ACCEPTED SOLUTION

Michael Ritchie
ServiceNow Employee
ServiceNow Employee

There is nothing special you need to do to enable grouping on a field, it should just show up.  Are there any ACLs on the field having issues?

View solution in original post

8 REPLIES 8

Michael Ritchie
ServiceNow Employee
ServiceNow Employee

There is nothing special you need to do to enable grouping on a field, it should just show up.  Are there any ACLs on the field having issues?

Rohit Kaintura
Mega Guru

Please load it again. Might be the form doesnot get loaded properly. Also, it can be a issue of report on acl. Please, check the same in acl.

Adam Robbins1
Mega Guru

I checked the Access Control tab and confirmed there is nothing tied to the field.  The strange thing is I tried the same steps in my personal instance and it did allow a Group by.  I've tried the following back in our Dev environment without success:

1) Deleted and re-created the field

2) Created a brand new field with a different name

I think next I might just try creating the field in the QA environment to see if it works.

Thanks,

Adam

Is your instance is domain seperated?