-
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
Issue with WaveAnalyticAssetCollection retrieval causing ENOENT error and missing folders #3095
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Any news? |
@Alfystar - there are 2 different problems here. One of them is server side and one of them in the CLI.
For issue 1 above, please open a support case so they can create an investigation for the owning server side team. Tell the Support rep that the owning team is called, "TUA-Collaboration Slack Experience" in the Tableau Unifed Analytics cloud. |
This issue has been linked to a new work item: W-17355528 |
@Alfystar - a fix for the CLI issue has been applied in the latest version of the deploy-retrieve plugin. If you'd like to test it out locally you can |
Description:
I encountered an issue when trying to retrieve
WaveAnalyticAssetCollection
metadata using the Salesforce CLI (sf-cli). The command used was:The
package.xml
used was:The command failed with the following error:
I created the missing directory manually:
However, the result was:
The directories I created were deleted during the process.
I obtained the list of
WaveAnalyticAssetCollection
using the command:sf org list metadata --metadata-type WaveAnalyticAssetCollection --target-org 'PROD_RM' --json
Here is a snippet of the result:
Request:
WaveAnalyticAssetCollection
retrieval causing the ENOENT error and the missing folders.System Information
The text was updated successfully, but these errors were encountered: