-
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
sf project generate manifest --from-org failing #2841
Comments
Hello @KevinGossentCap 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
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. |
Well, the metadata API giving back metadata without a type is definitely going to cause problems for consumers like the CLI. I'm really glad you found that...do you have any idea what that type is for ? Are you getting back that response from the metadata describe? Is there a way to construct a scratch org that has that in its mdapi responses so I can see it? |
Not sure if you searched issues, but you might want to look at #2229 (comment) |
Hi @mshanemc , I did not find any way to find what this ocmponent is as of now. I tried to add _Default to .forceignore but it did not change a thing |
Sounds like a SynonymDictionary https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_synonymdictionary.htm They _Default can get broken. I've found sometimes I need to recreate it as a different name and delete the original to get it represented correctly. I think there are probably a couple other open issues on this repo for the same problem. |
I played with CLI commands and duplicating/deleting through CLI makes things work afterwards. |
This issue has been linked to a new work item: W-15584672 |
marking this as a bug so we can make the CLI more resilient to bad behavior like this. |
@mshanemc the quickest idea would be to
|
I saw your PR and refactor afterwards, pretty clean 😄 |
@KevinGossentCap it's in |
This issue is fixed in version 2.39.6 of Salesforce CLI. |
Summary
In most of my Salesforce environments, the un restricted sf project generate manifest --from-org does fail with a pretty standard message
Error (1): _Default: Could not infer a metadata type
Try this:
Additional suggestions:
Confirm the file name, extension, and directory names are correct. Validate against the registry at:
https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json
If the type is not listed in the registry, check that it has Metadata API support via the Metadata Coverage Report:
https://developer.salesforce.com/docs/metadata-coverage
If the type is available via Metadata API but not in the registry
I played with CLI sources to try to find what it was and not a better thing as I get this in the listing
Steps To Reproduce
Can't find what's this _Default component but since I have it, everything just crashes
Expected result
No crashing !
For element/type not yet supported/described, more information so that we could give it/implement with a PR
Actual result
Crashes and no package xml produced
System Information
Additional information
The text was updated successfully, but these errors were encountered: