-
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 pbo" generates a manifest including unexpected installed package metadata #2759
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. |
This issue has been linked to a new work item: W-15247671 |
I reproduced it. Thanks for the excellent repro steps! |
I think this depends on the type of installed package. For managed and unlocked packages it behaves as expected, and you need to use the |
@shetzel No, I run the command without the In my example, you can see the CHANNEL_ORDERS and CodeBuilder packages which are both Salesforce-provided packages, but I'm pretty sure the same behaviour happens with other packages : their metadata is always retrieved, although I am not passing the |
Ok, I see what's happening. In short, it's a bug and maybe there's something the CLI can do to improve the accuracy, but the bug is with the server responses the CLI uses to distinguish between packaged metadata and non-packaged metadata. I'm going to create a few internal bugs for some server side teams to fix. I'll post bug numbers to this GH issue. When they are there, if you could contact support and point them to those internal bugs it will help prioritize the bug fixes with those teams. More info: From the snippet of the generated manifest you provided above, those entries are for the
There is no namespacePrefix or manageableState, which is why the CLI didn't exclude it from the manifest. You can see this yourself if you run this command: However, there might be a workaround for this that we can add. I think we should be able to first ask the org for installed packages, then use those entries as filters applied to metadata fullNames. |
@RupertBarrow - Here are the internally tracked bugs: W-15665146 for CustomObjectTranslations and W-15665627 for TopicsForObjects. If you see other types in your generated manifest please note them in this issue. Also, it helps get these fixes prioritized by the server teams if you contact support and ask them to attach cases to those issues. |
@shetzel In my case, I see this occurring on CustomObjectTranslation, CustomTab, Flow, Layout (of Custom Metadata), ListView, TopicsForObjects. I have opened Case #467310377 |
@RupertBarrow Not including CustomObjectTranslation and TopicsForObjects entries, are these the packaged metadata entries you're seeing?
If so, these are different in that the ListMetadata response entries are not wrong for all metadata. I'm not sure why certain entries are correct and others aren't. That mystery requires more investigation. Thanks for opening the case. I know that the owning team for CustomObjectTranslation has already started investigating the bug so it definitely helped. |
@RupertBarrow - are you reporting this because it's causing a problem in one of your workflows or because the behavior doesn't match the documentation? |
It's not (yet) a problem in my workflow. |
@RupertBarrow as this behaviour is related to the metadata api. The command In the <?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<name>CustomObjectTranslation</name>
<members>CodeBuilder__*</members>
</types>
<version>60.0</version>
</Package> |
% sf doctor
=== Running all diagnostics
pass - salesforcedx plugin not installed
pass - no linked plugins
pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
pass - [@salesforce/plugin-deploy-retrieve] default target DevHub max apiVersion matches default target org max apiVersion
pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches default target org max apiVersion
pass - using latest or latest-rc CLI version
Summary
sf project generate manifest --from-org
generates a manifest which mentions packaged metadata, when the default is that it should not (see the "-c" option).Steps To Reproduce
sf project generate manifest --from-org pbo -d .
./package.xml
and search for "CustomObjectTranslation" where, among others, you will find package metadata (eg "CHANNEL_ORDERS__" or "sfcma__")Expected result
The generated manifest file should not mention any packaged metadata
Actual result
The generated manifest file contains metadata of installed packages such as :
System Information
Shell : zsh
sf version --verbose --json :
Additional information
The text was updated successfully, but these errors were encountered: