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

[nvuillam]

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

[github-actions]

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]

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]

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.

[git2gus]

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

[github-actions]

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]

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

[Alfystar]

Hi every ones

I'm here to report that as of today, with version 2.76.6, it seems that the namespace problem for Translations has been solved, but it was present in 2.75.5.

I was wondering if something had been released about it