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

Translations are missing the namespace prefix of Apps from Managed Packages #2905

Open
amtrack opened this issue Jun 5, 2024 · 12 comments
Open
Labels
owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. validated Version information for this issue has been validated

Comments

@amtrack
Copy link

amtrack commented Jun 5, 2024

Summary

When retrieving Translations from a Source-Tracked Org, the <customApplications> entries are missing the namespacePrefix of Apps from Managed Packages (e.g. Address Picker Autocomplete for Flow).

As a consequence the deployment of those invalid .translation-meta.xml files to another org fails with:

In field: name - no CustomApplication named Address_Picker_Autocomplete found

Steps To Reproduce

Please see my Git repository for all details and a reproduction using GitHub Actions:
https://github.com/mdapi-issues/mre-translations-missing-namespace-of-applications

TL;DR

# create a Scratch Org with the Translation Workbench enabled
sf org create scratch -f config/project-scratch-def.json --alias translation-managed-application --set-default
# install the Managed Package "Address Picker Autocomplete for Flow"
sf package install --package 04t6F000004DJCEQA4 --no-prompt --wait 30
# deploy some unrelated translation of a managed CustomLabel
sf project deploy start --source-dir fixtures/some-unrelated-translation-of-a-managed-customlabel
# retrieve the translations from the Scratch Org
sf project retrieve start -m Translations

Expected result

<?xml version="1.0" encoding="UTF-8"?>
<Translations xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <customApplications>
        <description xsi:nil="true"/>
        <label><!-- Address Picker Autocomplete --></label>
        <name>DV_Flow_AP__Address_Picker_Autocomplete</name>
    </customApplications>
</Translations>

Actual result

<?xml version="1.0" encoding="UTF-8"?>
<Translations xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <customApplications>
        <description xsi:nil="true"/>
        <label><!-- Address Picker Autocomplete --></label>
        <name>Address_Picker_Autocomplete</name>
    </customApplications>
</Translations>

actual (red) vs. expected (green)

<?xml version="1.0" encoding="UTF-8"?>
<Translations xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <customApplications>
        <description xsi:nil="true"/>
        <label><!-- Address Picker Autocomplete --></label>
-        <name>Address_Picker_Autocomplete</name>
+        <name>DV_Flow_AP__Address_Picker_Autocomplete</name>
    </customApplications>
</Translations>

System Information

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.42.6",
  "nodeVersion": "node-v20.10.0",
  "osVersion": "Darwin 23.5.0",
  "rootPath": "/Users/john.doe/.local/lib/node_modules/@salesforce/cli",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.0.18 (core)",
    "@oclif/plugin-commands 3.3.4 (core)",
    "@oclif/plugin-help 6.0.22 (core)",
    "@oclif/plugin-not-found 3.1.9 (core)",
    "@oclif/plugin-plugins 5.0.21 (core)",
    "@oclif/plugin-search 1.0.24 (core)",
    "@oclif/plugin-update 4.2.12 (core)",
    "@oclif/plugin-version 2.1.2 (core)",
    "@oclif/plugin-warn-if-update-available 3.0.19 (core)",
    "@oclif/plugin-which 3.1.10 (core)",
    "@salesforce/cli 2.42.6 (core)",
    "apex 3.1.11 (core)",
    "auth 3.6.11 (core)",
    "data 3.3.5 (core)",
    "deploy-retrieve 3.6.14 (core)",
    "info 3.2.8 (core)",
    "limits 3.3.7 (core)",
    "marketplace 1.2.5 (core)",
    "org 4.1.10 (core)",
    "packaging 2.4.4 (core)",
    "schema 3.3.6 (core)",
    "settings 2.2.6 (core)",
    "sobject 1.4.2 (core)",
    "source 3.3.12 (core)",
    "telemetry 3.3.7 (core)",
    "templates 56.2.7 (core)",
    "trust 3.6.11 (core)",
    "user 3.5.8 (core)"
  ]
}

Additional information

image

Untitled

Screenshot 2024-06-05 at 16 00 29

@amtrack amtrack added the investigating We're actively investigating this issue label Jun 5, 2024
Copy link

github-actions bot commented Jun 5, 2024

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.

@github-actions github-actions bot added the validated Version information for this issue has been validated label Jun 5, 2024
@amtrack
Copy link
Author

amtrack commented Jun 5, 2024

Sorry for spamming you with issues related to the Metadata API. 😄

@mshanemc
Copy link
Contributor

mshanemc commented Jun 5, 2024

I'll add this to our list of items to discuss with them

@shetzel
Copy link
Contributor

shetzel commented Jun 5, 2024

Possibly related to this one (if you dig deep in that thread and take note of CustomObjectTranslation issues): #2759

As always with server side issues, it will greatly help get their attention with a customer support case.

@amtrack
Copy link
Author

amtrack commented Jun 5, 2024

Thanks @mshanemc @shetzel. I'll create a customer support case.

@frukeci
Copy link

frukeci commented Jun 17, 2024

Hi @amtrack, currently facing the same issue - is this still being investigated or did the support come up with a solution?

@amtrack
Copy link
Author

amtrack commented Jun 17, 2024

@frukeci I was told by Salesforce Support on the phone that a Known Issue will be created.

@amtrack
Copy link
Author

amtrack commented Jun 18, 2024

@frukeci Here's the Known Issue: https://issues.salesforce.com/issue/a028c00000zJBW9AAO. Please click "Report" to let Salesforce know this affects you.

@frukeci
Copy link

frukeci commented Jun 18, 2024

@amtrack Thank you! I reported it.

@gearsetdave
Copy link

We're seeing this for translations of a namespaced layout too, so I think the issue is wider than the known issue. I've clicked Report anyway 👍

@axmav
Copy link

axmav commented Jun 26, 2024

Same problem for us, we will very appreciate the fix.

@mshanemc mshanemc added owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. and removed investigating We're actively investigating this issue labels Jul 2, 2024
Copy link

github-actions bot commented Jul 2, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

6 participants