Closed MarcDBehr closed 12 months ago
Hi @MarcDBehr, I'm trying to repro this but even when running the sf command through the cli, the content of the xml is the same, with only the reference to the error. Could you send a screenshot of what you get when using our extensions and when sing the cli? Thanks in advance!
@CristiCanizales From the extension, it looks like:
`<?xml version="1.0" encoding="UTF-8"?>
Hi @MarcDBehr! Sorry for the delay. Could you tell me what's your sourceApiVersion
in your sfdx-project.json?
{ "packageDirectories": [ { "path": "force-app", "default": true } ], "namespace": "", "sfdcLoginUrl": "https://login.salesforce.com", "sourceApiVersion": "59.0" }
Could you try uninstalling sf cli
and installing sfdx cli
? Instructions here. Then, just try retrieving your flow. We've been playing around with versions and with sfdx cli it successfully retrieves the customErrors section. My sfdx version is: sfdx-cli/7.209.6 darwin-arm64 node-v18.15.0
But shouldn't we be moving away from from the sfdx CLI to the sf CLI? Are you suggesting that the extension does not work with the latest version of the CLI?
$ sf version @salesforce/cli/2.14.6 darwin-x64 node-v20.6.0 $ sfdx version @salesforce/cli/2.14.6 darwin-x64 node-v20.6.0
Yes, it's not mandatory though (yet). It was just to see if it worked for you and have more info to keep digging on the root cause.
Hi @MarcDBehr, As another try, could you please clean the cache by deleting the .sfdx and .sf folders from the Explorer (left panel) and deleting the flow that you retrieved, then reload the VSCode window by running "Developer: Reload Window" from the command palette? If that also does not fix the issue, please try restarting your computer. Thanks a lot for trying with us.
@daphne-sfdc I deleted the .sf and .sfdx folders and then I deleted the local version of the flow and reloaded the window. Next, I went to org browser and downloaded the flow and this time, I can see the error message correctly. So.... I guess there was something in the cache that was being referenced rather than the org itself? If so, this same thing happened to several people here, so this does not seem to be an issue on a single system.
Hi @MarcDBehr, Thank you very much for the confirmation, and glad to hear that everything is now working as expected on your system. We're not sure why there is the cache issue, and you're right that it's not specific to any orgs, projects, or systems - although the solution to clean the cache has worked in most cases. Closing this issue as completed.
Summary
We have a v59.0 flow that includes the new "Error Message" action. When the flow is downloaded using the extension (org browser or retrieve), a critical part of the flow (the customErrors section( is not retrieved.
Steps To Reproduce:
Expected result
The 'complete' flow version shoule be retrieved.
Actual result
Got a version of the flow that can't be deployed anywhere
Additional information
Feel free to attach a screenshot.
Salesforce Extension Version in VS Code:
v59.1.2
SFDX CLI Version:
@salesforce/cli/2.13.9 darwin-x64 node-v20.6.0
OS and version:
MacOS Version 14.0 (23A344)
VS Code version:
Version: 1.83.1 Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc Date: 2023-10-10T23:46:55.789Z (1 wk ago) Electron: 25.8.4 ElectronBuildId: 24154031 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Darwin x64 23.0.0