Error during CustomObjectTranslation retrieve with sf-cli - (sf project generate manifest) #3215
Labels
investigating
We're actively investigating this issue
validated
Version information for this issue has been validated
Comments
|
Hello @Alfystar 👋 None of the versions of Shared: Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue. After updating, share the full output of |
|
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
bot
added
more information required
Alfystar
changed the title
|
Run the command below and check the output. If you see those 2 problem entries in the output (and I'm guessing you will) then that's how the
|
|
Hi @shetzel As you can see, the problem is present also using "list metadata" and from what I can see, it seems to hit all resources that are installed in a package. For now this regex seems to work (to identify translate resources): |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
While executing our parallel full-retrieve procedure, we encountered an unusual error during the retrieve of CustomObjectTranslation. The command used and the error encountered are detailed below.
Command:
Error:
Analysis:
After thorough analysis, we discovered that the issue pertains to two specific resources:
APXTConga4__en_USAPXTConga4__esThese resources do not follow the
<ResName>-<Language>pattern, unlike other resources such as:ATN_Asignaci_n_de_casos__c-esATN_AsignacionPedidos__c-esATN_AsignacionUsuarios__c-esATN_Asignacion_AGT_Emp__c-esThe list was generated using the command:
Workaround:
For now, we are excluding
CustomObjectTranslationthat do not end with-<Language>, but we believe this is a bug in thesf-clior the org.Complete list of resources not following the pattern:
Conclusion:
We believe this issue is a bug in the
sf-clior the org. Please investigate further and provide a solution.System Information
{ "architecture": "darwin-arm64", "cliVersion": "@salesforce/cli/2.76.7", "nodeVersion": "node-v23.7.0", "osVersion": "Darwin 24.3.0", "rootPath": "/opt/homebrew/lib/node_modules/@salesforce/cli", "shell": "zsh", "pluginVersions": [ "@oclif/plugin-autocomplete 3.2.20 (core)", "@oclif/plugin-commands 4.1.19 (core)", "@oclif/plugin-help 6.2.24 (core)", "@oclif/plugin-not-found 3.2.40 (core)", "@oclif/plugin-plugins 5.4.30 (core)", "@oclif/plugin-search 1.2.20 (core)", "@oclif/plugin-update 4.6.30 (core)", "@oclif/plugin-version 2.2.23 (core)", "@oclif/plugin-warn-if-update-available 3.1.32 (core)", "@oclif/plugin-which 3.2.28 (core)", "@salesforce/cli 2.76.7 (core)", "apex 3.6.8 (core)", "api 1.3.3 (core)", "auth 3.6.92 (core)", "data 4.0.9 (core)", "deploy-retrieve 3.18.0 (core)", "info 3.4.37 (core)", "limits 3.3.45 (core)", "marketplace 1.3.7 (core)", "org 5.2.29 (core)", "packaging 2.9.16 (core)", "schema 3.3.49 (core)", "settings 2.4.14 (core)", "sobject 1.4.50 (core)", "telemetry 3.6.32 (core)", "templates 56.3.37 (core)", "trust 3.7.61 (core)", "user 3.6.8 (core)", "sfdx-plugin-source-read 0.0.0-development (user) published NaN days ago (Invalid Date) (latest is 1.4.2)" ] }The text was updated successfully, but these errors were encountered: