OmniProcess Metadata Type Unsupported

[ThomasSmithIRE]

Summary

2.45.6 failing to retrieve OmniProcess metadata from source org.

Steps To Reproduce:

1. Enable OmniStudio Metadata in OmniStudio Settings in target org.
2. Add the OmniProcess type with either a wildcard member reference, or a component unique name.
3. Perform a SF retrieve on the manifest file.

Expected result

The OmniStudio metadata is retrieved successfully and the folder with the metadata files is created in the package.

Actual result

Additional information

https://help.salesforce.com/s/articleView?id=sf.os_enable_omnistudio_metadata_api_support.htm&type=5

Salesforce Extension Version in VS Code: Salesforce Extension Pack v61.0.1

Salesforce CLI Version: 2.45.6

OS and version: macOS Monterey v12.5

VS Code version: Version: 1.87.1

Most recent version of the extensions where this was working: N/A

[svc-idee-bot]

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.

[svc-idee-bot]

Hello @ThomasSmithIRE :wave: It looks like you didn't provide all the required basic info in your issue.

If you haven't already, please provide the following info: Salesforce Extension Version in VS Code: Salesforce CLI Version: OS and version: VS Code version: Most recent version of the extensions where this was working:

Here's an example of a set of required info that will pass the validation: Salesforce Extension Version in VS Code: 60.13.0 Salesforce CLI Version: @salesforce/cli/2.42.6 darwin-arm64 node-v18.18.2 OS and version: MacOS Sonoma 14.5 VS Code version: 1.89.1 Most recent version of the extensions where this was working: 60.11.0

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue, as well as all error messages that you see.
  • A repository that clearly demonstrates the bug is ideal.
  • Error messages can be found in the Problems Tab, Output Tab, and from running Developer: Toggle Developer Tools in the command palette.
• Make sure you've installed the latest version of the Salesforce Extension Pack for VSCode. (docs)
• Search GitHub for existing related issues.

Thank you!

[diyer]

@ThomasSmithIRE Looks like you are not using vs code extension to run this command but instead you are calling the cli command. If this issue is when running the cli command, we will transfer this issue to the appropriate team.

[ThomasSmithIRE]

@diyer it is the same result when using the vscode extension through cmd-shift-p i.e SFDX: Retrieve Source in Manifest from Org

{
  "key": "",
  "command": "sf.retrieve.in.manifest"
}

[ThomasSmithIRE]

@diyer why has this item moved? It's an issue with both CLI and Plugin.

[CristiCanizales]

Hi @ThomasSmithIRE! Sorry! I misread the comment about the transfer and just transferred. Anyways extensions and CLI both use SDR library so when it's an issue with both it's usually something there or with metadata api tooling. I'll be looking into this anyways as well to see if I find what's going on

[ThomasSmithIRE]

@CristiCanizales any update on this?

[git2gus[bot]]

This issue has been linked to a new work item: W-16205934

[svc-idee-bot]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

[daphne-sfdc]

Hello @ThomasSmithIRE, We have determined that this issue is a bug that is owned by another team. Here is a public doc with what metadata types are currently supported and can be retrieved: https://dx-extended-coverage.my.salesforce-sites.com/docs/metadata-coverage/61 - OmniProcess is currently not in that list and support for it will need to be added in the backend.

I have filed a bug with the team that owns the OmniStudio data types and let them know all the details. We'll be keeping this issue open for visibility in case others are also facing the same issue.

Sorry for the inconvenience.

[diyer]

@ThomasSmithIRE since this issue is owned by another team and the fix is not within our realm, we recommend opening a Salesforce case and assigning it to the appropriate team to look into this. Please let us know if you have any more questions or anything we can help with.