Skip to content
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

sfdx force:source:manifest:create --fromorg retrieving wrong Layout names when they are packaged #2168

Open
nvuillam opened this issue May 26, 2023 · 6 comments
Labels
bug Issue or pull request that identifies or fixes a bug owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team.

Comments

@nvuillam
Copy link

nvuillam commented May 26, 2023

sfdx force:source:manifest:create --fromorg retrieving wrong Layout names when they are packaged

This is exactly the same bug than the following, the namespace is missing when the layout is related to a managed package object

dxatscale/sfpowerkit#226

Example:

Generated manifest contains:

sofactoapp__Factures_Client__c-Sofacto_Facture_PL_v3

Manifest should contain:

sofactoapp__Factures_Client__c-sofactoapp__Sofacto_Facture_PL_v3

cc @mamasse19

@nvuillam nvuillam added the investigating We're actively investigating this issue label May 26, 2023
@github-actions
Copy link

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.

@amtrack
Copy link

amtrack commented May 31, 2023

I've ran into this issue in the past with listMetadata().
AFAIK it also affects QuickAction and CustomMetadata.
So I've created a reproduction for this issue with a workaround: https://github.com/mdapi-issues/listmetadata-installed-missing-namespaceprefix

@LukasPIT
Copy link

LukasPIT commented Jun 6, 2023

This also affects translations.
At one of my customers, we had the issue that de.translation-meta.xml was retrievable, but not deployable due to components (Layouts, Reports, Dashboards) in the file from FinServ namespace, wich didn't include this namespace in the file and therefore deployment failed, because these components can't be found without the namespace.

@cristiand391 cristiand391 added bug Issue or pull request that identifies or fixes a bug and removed investigating We're actively investigating this issue labels Jun 7, 2023
@git2gus
Copy link

git2gus bot commented Jun 7, 2023

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

@mshanemc mshanemc added the owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. label Nov 16, 2023
Copy link

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.

@mshanemc
Copy link
Contributor

Hey, there's nothing CLI can do about this. I'll have our PM talk to their PM and try to get it fixed.

Thanks for the excellent repro as always @amtrack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team.
Projects
None yet
Development

No branches or pull requests

5 participants