Closed jesuRule closed 3 years ago
This issue has been linked to a new work item: W-9300215
@jesuRule we're trying to figure out what the correct format should be. What tool are you using that's producing encoded filenames that don't match the CLI?
I am using this encoder: https://coderstoolbox.net/string/#!encoding=url&action=encode&charset=utf_8
We're going to leave the accents marks.
They deploy and retrieve properly as is. If we were to change them to encode, it would be disruptive to people's source-based projects.
Summary
When retrieving metadata with accent marks (for example, a Profile named "Atención"), these characters are not encoded in the local file system. Is this the expected?
Other special characters are do encoded such as forward slashes, backslashes, quotation marks or commas.
Steps To Reproduce:
sfdx force:mdapi:retrieve -u TARGETUSERNAME -r RETRIEVETARGETDIR -k UNPACKAGED -w -1
Expected result
Profile downloaded in local file system with encoded name? -> "Atenci%C3%B3n.profile"
Actual result
Profile name is not encoded. Profile name: "Atención.profile".
Additional information
A manual encoding is needed before deploying back the Profile, otherwise an error is faced:
UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 511692291-249672 (-375156510).
SFDX CLI Version:
sfdx-cli/7.74.1-32db2396ed win32-x64 node-v12.18.3
SFDX plugin Version