Hello, I’m running into an error while trying to clone a workspace using

gd clone

(GoodData Analytics CLI v0.23.0). Here’s the error I’m getting:

[e] Command failed with error
[e] Error: Reference type is not supported. Item: undefined
    at t.newError (\AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:600842)
    at u (\AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:573987)
    at k (\AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:493729)
    at w (\AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:492332)
    at \AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:491735
    at Array.forEach (<anonymous>)
    at P (\AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:491715)
    at \AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:501389
    at t.declarativeVisualisationToYaml (\AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:501743)
    at \AppData\Roaming\npm\node_modules\@gooddata\code-cli\out\index.js:14:515780 {
  type: 'ReferenceTypeNotSupported',
  code: 'core.referenceTypeNotSupported'
}

One more thing - I’m able to clone child workspaces, but the cloned result only includes the metrics/visuals/dashboards created directly in that child workspace. It doesn’t include any metrics or datasets coming from the master workspace. Could you please help me understand what might be going wrong here? Thanks! Geetha

You’re hitting two separate, but related, limitations of the current GoodData CLI. 1.

ReferenceTypeNotSupported

error in

gd clone

This error has been seen before when cloning a workspace: it indicates that some dashboard or visualization is using a component/layout/visualization type that the current CLI version does not yet support. Updating the CLI to the latest version resolved it in that case. [CLI docs; Similar error] What to do: 1. Upgrade the CLI globally to the latest version:

npm i -g @gooddata/code-cli
   gd -v

2. Re‑run

gd clone

in a clean folder (or with

gd clone -f

if you’re OK overwriting the

analytics

folder). [CLI docs] If the error persists even on the latest version, it likely means there is still an unsupported visualization/layout type in that workspace. In that case, you’ll need to share the workspace details with GoodData Support so engineering can reproduce and extend CLI support (similar to how other CLI issues were handled). [CLI beta limits] 2. Child workspace clone missing inherited content What you’re seeing with child workspaces is expected with the current CLI: • GoodData CLI and the VS Code extension are beta and currently work on a *single workspace only*; they do not support hierarchies or child workspaces. [CLI hierarchy limits] • When you clone a child workspace, you only get the objects created directly in that child; inherited objects from the parent (master) workspace are not pulled into the child’s YAMLs. [CLI hierarchy limits; Backup guidance] There is currently no supported way to have

gd clone

produce a full, deploy‑ready YAML snapshot that includes both parent and child workspace assets together. For parent–child setups and workspace data filters, the recommended tooling is the Python SDK / declarative APIs, not the CLI. [Backup hierarchies] ------------------------- Summary • Update

@gooddata/code-cli

to the latest version and retry

gd clone

to address the

ReferenceTypeNotSupported

error. • The missing inherited content in child workspace clones is a known limitation: CLI does not yet support hierarchies, so only child‑local objects are cloned. • For full parent+child management/backup, use the declarative Workspace APIs or Python SDK instead of relying solely on `gd clone`/`gd deploy`. 👍 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 Geetha. Reviewing our AI answer: 1. About the child workspace clone missing inherited content - it's true This is not a supported feature yet. 2. Cloning error - as I see, you are using our latest CLI version. CLI tool is currently in beta and is therefore prone to errors like this. As a first step, I would recommend starting fresh by removing the current project's directory, if possible, and then trying again. If the issue persists, could you let us know if you introduced any changes to the workspace, e.g., are you using any dashboard plugins, custom visualizations, or special configuration for your date filters? Ideally, please send over a JSON definition of the workspace from

GET https://<your_domain>/api/v1/layout/workspaces/{workspaceId}

for closer inspection. GoodData CLI is currently still under active development. Do not use beta features in your production environment.

Hi Shamil, Thanks for the clarification regarding the inherited content. I haven’t introduced any changes to the workspace - this is a newly migrated workspace from the platform, and I’m currently exploring the options available with the GoodData CLI. I deleted the project directory and tried cloning again, but I’m still getting the same error. I’m trying to clone a POC workspace. Could you please help me understand what might be going wrong here?

Hi @Geetha Mosali. Based on the information you provided about it being from a migrated workspace, I believe that the problem is caused by the current CLI beta being unable to properly serialize some of the visualization objects. The main suspect seems to be the

pushpin

visualization in

08 Geographical Statistics

. I would recommend attempting the clone without that dashboard (you could copy the workspace and modify it, for example).

Hi Francisco, I changed the visualization to a table, confirmed in the JSON that there’s no pushpin, and even tried starting fresh in a new folder - but I’m still seeing the same error. So I don’t think pushpin is the issue here. Is there anything else I should be checking? Also, when we run into errors like this, what’s the best way to debug and identify which visual might be causing it? Thanks! Geetha

At this point in its development, the CLI tool is not very descriptive as I’d like, so troubleshooting it is a bit tricky. My strategy is to look at the workspace being cloned and check it for suspicious or unusual things that the tool might have trouble handling - but as you said, removing these visualizations didn’t help much. I’m working on my own instance, and must say that I was unable to reproduce this behavior. I think it relates to the fact that the workspace has been migrated - from GoodData Platform, correct? Would you tell me a bit more about the particular task you’re running? Is it just the initial

gd clone

command to get the workspace on your local environment? Were you able to get it to run with any other workspace, perhaps a simpler one, or one that hasn’t been migrated?