Report of fields used in reports

Hi Annette Shultz ,

This data is not something you could build a report out of Sugar in an easily readable format. Sugar stores all of the field filter and layout contents in a single database column (saved_reports.content) and the content format is like the following:

{
    "display_columns":[
        {
            "name":"name",
            "label":"Account Name",
            "table_key":"self"
        },
        {
            "name":"phone_office",
            "label":"Phone Office",
            "table_key":"self"
        },
        {
            "name":"description",
            "label":"Description",
            "table_key":"self"
        },
        ...

You could get a report with these contents by creating an Advanced Report custom query like the following:

SELECT content FROM saved_reports WHERE deleted = '0';

Then with that output, you can work with data outside of Sugar to extact the field names in an easier to read format. It's not ideal, but I'm not aware of a better solution to your use case. 

Chris

Hi Annette Shultz ,

This data is not something you could build a report out of Sugar in an easily readable format. Sugar stores all of the field filter and layout contents in a single database column (saved_reports.content) and the content format is like the following:

{
    "display_columns":[
        {
            "name":"name",
            "label":"Account Name",
            "table_key":"self"
        },
        {
            "name":"phone_office",
            "label":"Phone Office",
            "table_key":"self"
        },
        {
            "name":"description",
            "label":"Description",
            "table_key":"self"
        },
        ...

You could get a report with these contents by creating an Advanced Report custom query like the following:

SELECT content FROM saved_reports WHERE deleted = '0';

Then with that output, you can work with data outside of Sugar to extact the field names in an easier to read format. It's not ideal, but I'm not aware of a better solution to your use case. 

Chris