Hello! I'm using

@gooddata/code-cli@0.23.0

and it appears that when doing a

gd clone

, dashboard level interaction modifications for individual visualizations is not getting included. In my use case, I have a table with drill interactions on attributes, and while the drill interaction is included, a reduced set of drilled data point filters is not.

You’re running into a limitation of the current GoodData CLI / VS Code “Analytics as Code” tooling. From the available information: • GoodData CLI is still a beta feature and works only on a single workspace, with several known gaps around more advanced dashboard behavior (hierarchies, WDFs, filter contexts, some visualization details, repeaters, etc.). [CLI beta limits; Parent/child limits] • There are known issues where not all visualization configuration is preserved when cloning/deploying via CLI (e.g., extra color labels, repeater visualizations, some filter-related behavior). [Color labels stripped; Repeater issues] • Filter contexts and some advanced filter handling are not fully supported by `gd clone`/`gd deploy`; for example, filter contexts are ignored by CLI and only handled by the Python SDK. [Filter contexts & CLI] The docs clearly describe that dashboard drill interactions can be configured to pass only a subset of filters (“Pass as filters” configuration), but there is no documentation stating that this fine‑grained drill filter configuration is captured by

gd clone

. [Disable passing filters] Putting this together: • It is very likely that

gd clone

currently does not serialize the “Pass as filters” / reduced drill filter configuration for interactions, and only the basic drill interaction (target visualization/dashboard) is captured. • This matches the pattern of other missing/partial features in the CLI beta. Because the knowledge sources do not explicitly confirm this specific limitation, I cannot state it as official behavior, but everything available strongly suggests it is a current gap in

@gooddata/code-cli

. Practical recommendations: 1. Treat this as a current limitation of

@gooddata/code-cli

0.23.0. 2. If you need to preserve these drill filter settings in code-based workflows, consider: ◦ Using the Python SDK to store and restore the full analytics model (including filter contexts and more advanced configuration) as YAML, where supported. [Python SDK model export] 3. Report this as a product issue/feature request via your GoodData contact or Community Slack so it can be prioritized for future CLI versions, similar to other reported CLI gaps. [CLI feedback & roadmap] If you can share a minimal example (one dashboard + one table with a reduced “Pass as filters” setup) with Support, they should be able to confirm and log it directly with engineering. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

Hi Thanh, we have reviewed the response from our AI Assistant, and it may be a limitation in GoodData CLI tool - However, if you could please provide more details on your specific use-case, and clarify for me when you say “data point filters”, I will be happy to clarify this for you and provide product feedback if necessary.

Thanks for the response, Michael. For the current use-case that I'm looking at, I'm accessing selections through the attached flow:

Hi Thanh, thank you for your patience on this and our apologies for this radio silence. We have been checking and testing this internally and we are able to reproduce the behaviour. Our team in charge of the code-cli feature is aware of this, but at this moment I can not provide any ETA.