This message was deleted GoodData #gooddata-cloud

Join Slack

This message was deleted.

# gooddata-cloud

Slackbot

07/01/2024, 7:11 PM

This message was deleted.

Michael Ullock

07/01/2024, 10:31 PM

Hi Patrick, yes, this is the expected behavior that running

gd deploy

via the CLI resets the saved filter contexts for logged in embedded users. The

deploy

command replaces the entire workspace with the local analytical objects, which overwrites any existing filter settings.

deploy

is designed to completely replace the workspace, which has the side effect of resetting the filter contexts. Using

clone

or manually setting the filters after deployment would be the best ways to maintain the saved filter settings when updating the objects.

Tomas Muchka

07/02/2024, 6:43 PM

Hello Patrick,

gd clone

currently does not take filter contexts into account. Only our Python SDK does so. As @Michael Ullock mentioned,

gd deploy

replaces the full workspace content. To be sure I understand the issue completely, can you describe me the situation after deploy? I’m interested to understand how how does this filter reset your users experience look like, Thanks in advance.

Tomas Muchka

07/02/2024, 6:46 PM

Here is a link to the Python SDK method that stores analytics model (including filter contexts) as YAML files. https://www.gooddata.com/docs/python-sdk/latest/workspace-content/analytics-model/store_analytics_model_to_disk/

Tomas Muchka

07/03/2024, 8:48 AM

Hi Patrick, to be honest this is the first time we hear about these kind of issues, thus the work with filter contexts in GoodData for VS Code is not planned at the moment. I still would like to better understand how does your workflow look like. Do I understand correctly that you create and save the filter contexts for specific users? To mimic a missing functionality of GoodData?

7 Views

Open in Slack

Previous Next