-
Notifications
You must be signed in to change notification settings - Fork 238
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
Add support for space & tab in concat delimiter #278
Comments
…ens and multiple BR/token support Add support for Space (SP()) and Tab (TB()) tokens; Add support for multiple tokens (including existing BR()) in delimiter
I want this feature too. I would definitely want the ability to have a space after a semicolon or comma. |
Fixed in v2.2. |
Hi folks. I just installed DLRS and it's awesome! However, I tried using ", " as a delimiter and I noticed that the trailing space is getting removed. Is there a special format I need to enter to add a space at the end of the comma? More details: when I enter ", " and save it and go back to edit the field, it refreshes with "," Thanks! Much appreciated! Sam. |
Have you tried ",SP()" ? |
Perfecto, my man! Thanks. |
SFDC appears to "trim" leading/trailing whitespace on text fields. When inputting "; " or " ; " in concat delim, the data stored in the record itself does not contain the leading/trailing whitespace. Anonymous APEX results in the same behavior. For this reason, specific tokens are required to be added to support leading & trailing whitespace in the concat delimiter.
Use Case - For a semi-colon delimited list of values, need to be able to separate the values with a space after the semi-colon to make the list easier to read.
If anyone is aware of a way to avoid the whitespace being trimmed prior to record insert/update, I'd love to hear it! :)
Proposal is to add SP() and TB() tokens to provide for single space and tab character in delimiter.
The text was updated successfully, but these errors were encountered: