In my analytical designer, the groups in the catalog are expanded by default. How can I get them to be collapsed by default? I found some documentation about Default folder state and ADCatalogGroupsExpanded here: https://help.gooddata.com/doc/growth/en/dashboards-and-insights/analytical-designer/work-with-metrics/data-catalog-in-analytical-designer/ And that leads to here: https://help.gooddata.com/doc/growth/en/workspace-and-user-administration/administrat[…]ce-objects/configure-various-features-via-platform-settings/ I tried to visit gray page

https://{<http://your.domain.com|your.domain.com>}/gdc/projects/{workspace_id}/config/

for a particular workspace but I get a 404 error. Since that was a deadend I tried following this which led me to here: https://help.gooddata.com/doc/enterprise/en/expand-your-gooddata-platform/api-reference/#tag/hierarchical-configuration But I don't think I am on enterprise. I've looked through the api reference and I don't see any obvious ways to change the setting..

Hi Jeremy, thanks for reaching out, happy to help. I noted that the documentation you attached is for our Platform product. After running some checks I noted that you are currently using Gooddata Cloud services, therefore the platform documentation would not be of great help in this case. Secondly, when you mention “groups in the catalog” does this mean Data catalogs in the analytical designer? If yes, you can find some detailed information about reviewing and organizing data catalogs on Gooddata Cloud in our documentation here. If not, may you please share some screenshots of what it currently looks like and what you would prefer, to allow us assist you further. Kindly let us know if this helps.

We would like for these to be collapsed by default like so:

Hi Jeremy, I will pass this question to our internal product team to find out if this is possible. Feedback will be shared with you as soon as possible. Thanks for your patience

Thanks!

Hi Jeremy, Thanks for your patience. I have some feedback regarding the data catalogue question that was asked earlier. It is possible to change the default setup of your data catalogue in the analytical designer to appear entirely collapsed. This can be done via API calls.This property can be set on workspace level, user level or Organization level. Please refer to the parameters shared below: Creation of property on workspace level:

POST: {{hostname}}/api/v1/entities/workspaces/{{workspaceId}}/workspaceSettings

{
  "data": {
    "type": "workspaceSetting",
    "id": "ADCatalogGroupsExpanded",
    "attributes": {
      "content": {
        "value": false
      },
      "type": "AD_CATALOG_GROUPS_DEFAULT_EXPAND_STATE"
    }
  }
}

Organization level:

{{hostname}}/api/v1/entities/organizationSettings

{
  "data": {
    "type": "organizationSetting",
    "id": "ADCatalogGroupsExpanded",
    "attributes": {
      "content": {
        "value": false
      },
      "type": "AD_CATALOG_GROUPS_DEFAULT_EXPAND_STATE"
    }
  }
}

User level

{{hostname}}/api/v1/entities/users/{{userId}}/userSettings

{
  "data": {
    "type": "userSetting",
    "id": "ADCatalogGroupsExpanded",
    "attributes": {
      "content": {
        "value": false
      },
      "type": "AD_CATALOG_GROUPS_DEFAULT_EXPAND_STATE"
    }
  }
}

To update the existing property, append ID of the property to the endpoint URL, and send the request as PATCH, for example for workspace:{

{hostname}}/api/v1/entities/workspaces/{{workspaceId}}/workspaceSettings/ADCatalogGroupsExpanded

Let me know if this works or if any further assistance is needed.

Amazing!! Thank you so much, we will give it a shot.

Hello, I am following up in this thread to continue with the issue. Jeremy was able to implement this settings change on a organizational level back in July had it was successfully working to collapse all groups until the beginning of this week and then it reverted to being expanded on default. I went and check out setting in the api and found it was set to false. I have tried toggling the organizational settings to true and then back to false without success. Any idea why this would have suddenly stopped working or what to do about it?

Hi Grant, Thanks for sending this in. We’ll review it internally and get back to you with our findings. In the meantime, can you confirm if anything was changed on your side that could have caused this?

Hi Grant, the issue seems to be on our side. I have reported this to our developers and will circle back to you with an update as soon as it becomes available. Thank you for your patience in the meantime.

Hi Grant, Thanks for your patience while we worked on this. I’m happy to let you know that the issue has been resolved. You can find the setting at the following endpoint:

/api/v1/entities/workspaces/{{workspaceId}}/workspaceSettings/

Once you locate it, make a GET request to:

/api/v1/entities/workspaces/{{workspaceId}}/workspaceSettings/mySetting

Then, copy the response body and use it to make a PATCH request to the same endpoint . Just update the value to

"false"

Thanks! Yes I already had that setting activated so it when you resolved the issue it took effect automatically on my end. Thanks for solving so quickly