-
Notifications
You must be signed in to change notification settings - Fork 78
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
Validation rule error messagess containing line breaks get "translated" with two whitespaces on deployment #3114
Comments
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. |
hi @svenfinitiv - is this an error in the org, or with the CLI? It sounds like you're able to deploy these translations (or lack of) and error message files ok, but when they're seen in the org, in a flow, they're not displayed correctly? If that's true, what is the difference between your local translation file, and what is written by a |
Hi @WillieRuemmele, there is no issue with the CLI per se, as we can retrieve and deploy the "empty" translations, but when using these in the org, the symptoms occur. Regarding the differences: When retrieving from the source sandbox, we get this result, take note of the line breaks before and after the comment:
After deploying to the target sandbox and reretrieving from there, we get this result:
|
@svenfinitiv - I would suggest raising a case directly with Salesforce |
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. |
Summary
We have some validation rules with line breaks, retrieve and deploy work so far, but when a flow hits this validation and should show the error, only an empty text is displayed. The default record page shows the original error message.
Steps To Reproduce
Given:
Steps:
Tip
use
sf doctor --create-issue
to automatically fill the required informationExpected result
Actual result
Additional information
System Information
The text was updated successfully, but these errors were encountered: