-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR running force:source:retrieve: Cannot read property 'getWorkspaceElements' of undefined #78
Comments
Could you narrow down the package.xml to determine which metadata type is causing the problem. We've done a lot with WaveTemplateBundle. I'm guessing one of the other types is causing this. |
Good thinking @reidaelliott. However, it turns out that If I comment out The interesting thing is that it still manages to retrieve metadata into the Here's the folder structure in VS Code if it's gonna be of any help: |
I have reproduced the problem as well. Will report back when we have a solution. Thanks |
Fix has been put in place and I believe it will roll out this week. thanks for making us aware of this. |
Hello , I am having the Same issue but for me it is reproduced for Reports and Dashboards . ERROR running force:source:retrieve: Cannot read property 'getWorkspaceElements' of undefined |
@tony-tawk-ei the fix that was put in was specific for WaveTemplateBundle and the retrieve command. It sounds like this is happening for a different metadata type? can you confirm it is not WaveTemplateBundle? |
I am using package.Xml generator extension for VScode in order to construct my manifest package. Xml file When I right click on package.Xml to sfdx retrieve I had this error in vscode When I removed reports and dashboards from package.xml the error disappeared on retrieve action. Sent from my Huawei phone-------- Original Message --------Subject: Re: [forcedotcom/cli] ERROR running force:source:retrieve: Cannot read property 'getWorkspaceElements' of undefined (#78)From: Reid Elliott To: forcedotcom/cli CC: tony-tawk-ei ,Mention @tony-tawk-ei the fix that was put in was specific for WaveTemplateBundle and the retrieve command. It sounds like this is happening for a different metadata type? can you confirm it is not WaveTemplateBundle?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
|
@reidaelliott I'm having the same issue with my package.xml:
I added items back one at a time and found the culprit: Did something change with StaticResource? I haven't had issues with this package.xml until today. |
I ran it using the latest cli installer (sfdx-cli/7.8.1-8f830784cc darwin-x64 node-v10.15.3) against my local server: |
@reidaelliott I get the same error with sfdx-cli/7.22.0-de5c6ecff8 darwin-x64 node-v10.15.3 sfdx force:source:retrieve -x "/Users/kaush/Workspace/EA Templates/EAApp/manifest/package.xml" Only happens when I add WaveTemplateBundle to the package.xml |
I saw this note : uninstalled SFDX CLI and reinstalled it and retrieve started working. Before I uninstalled it, I had @salesforce/analytics in the plugins along with analytics. After reinstalling I now have just analytics. I suspect @salesforce/analytics was an old plugin maybe? Some people have had to uninstall and reinstall sfdx to force update the version. @salesforce/analytics is a separate plugin for commands to use against Einstein analytics projects. |
someone else just hit this too and running 'sfdx:plugins update' should get everything working too. We also just released a new version 0.8.0 of @salesforce/analytics with some new features |
I'm getting the same error using sfdx-cli v7.22.0 and analytics plugin v0.8.0 |
interesting, and this is for a wavetemplatebundle metadata type? This was fixed in the core sfdx-cli has nothing to do with the analytics plugin, but seems like your on the latest versions of both. |
Yes, taking part in analytics workshop today and updated/installed everything.
|
I'd like to get a copy of this metadata to see if I can reproduce. Is it easily available? What if you run with just sfdx force:source:retrieve -m WaveTemplateBundle |
It is on an analytics playground org, I can send you the login in private. |
Thanks. are you currently in the class with Skip Sauls? |
Yes, I am. |
I think he hit the same problem and somehow was able to get around it, check with him. He can get me the reproducer too if necessary |
Talking to Skip, I get the same message below every time I run
|
thanks. we'll get that updated should just be a warning. and also reproduced the getWorkspaceElements error so will look into it. It seems the retrieve does work regardless of this error so hopefully not a blocker. |
We use Illuminated Cloud 2 plugin for IntelliJ IDEA, not Visual Code, and the error is failing the process in our case. |
fix was made today for sfdx force:source:retrieve of waveTemplateBundles - it should roll out tomorrow |
Working with sfdx-cli 7.23.1 |
Not working on
Just tried this morning although the metadata seems be retrieved nonetheless |
I am also getting the same error while running |
It seems like 'getWorkspaceElements' error message can occur with different metadata types. This thread and what I've fixed is only related to WaveTemplateBundles. That should be fixed. It might be most effective to start a new thread for issues with Territory2 . @AQTectonic I am guessing the members in your package.xml are something besides WaveTemplateBundles? |
if you have this in your package.xml it does n't work <types>
<members>*</members>
<name>ApexTestSuite</name>
</types> but it was working... |
The fix was made for WaveTemplateBundles. If you are still experiencing issues please create a new issue |
Getting the same error all of sudden for AuraDefinitionBundle
|
ERROR running force:source:retrieve: path must not be empty please help thanks in advance |
Summary
Created a project with manifest and tried to retrieve Wave (Einstein Analytics) components in order to setup source control and CI/CD with them, however, I'm receiving an error in the output.
I am using the sample Developer Edition org provided in Trailhead, so the issue should be easy to reproduce.
Steps To Reproduce:
SFDX: Create Project with Manifest
SFDX: Authorize an Org
from step 1.manifest/package.xml
content with belowpackage.xml
and executeSFDX: Retrieve Source in Manifest from Org
Expected result
All
Wave*
components from the org should have been retrieved, and the command should exit with code 0 (i.e. without any errors).Actual result
Some (or all? Not sure how to verify.) wave components get retrieved into
force-app/main/default/wave
andforce-app/main/default/waveTemplates
folders, the command exits with code 1 and the below error is reported in the output:VS Code Version:
Version: 1.33.0 (system setup)
Commit: 0dd516dd412d42323fc3464531b1c715d51c4c1a
Date: 2019-04-04T15:14:28.026Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763
SFDX CLI Version:
OS and version:
Microsoft Windows 10 Pro 10.0.17763
The text was updated successfully, but these errors were encountered: