The characters included in the Date format string are interpreted as a custom format and time string. Add a standard specifier to define how the desired information is displayed.
The date format can be important to make the document easier to read.
FORMAT SPECIFIER
DESCRIPTION
example
{! Tag | API name(d)}
Short date
01/09/2023
{! Tag | API name(D)}
Long date
Monday September 10, 2023
{! Tag | API name(f)}
Long date+short hour
Monday September 10, 2023 13:30
{! Tag | API name(F)}
Long date+long hour
Monday September 10, 2023 13:30:50
{! Tag | API name(g)}
Short date+short time
10/09/2023 13:30:50
{! Tag | API name(G)}
Short date+short time
10/09/2023 13:30
{! Tag | API name(M)}
Month+day
September 10
{! Tag | API name(R)}
RFC1123
Monday, September 10, 2023 13:30:03
{! Tag | API name(T)}
Long hour
13:30:50
{! Tag | API name(t)}
Short hour
13:30
{! Tag | API name(Y)}
Date+month
September 2023
{!Label|APIName(dd MMMM yyyy)}
You can create complex tags with the following format specifiers in the form {!Object|Field(dd MMMM yyyy)} for example. You can also choose to use hyphens or “/” between each date format.
01 09 2023
{!Label|APIName(d)}
Day of the month, from 1 to 31
1
{!Label|APIName(dddd)}
Full name of the day of the week
lundi
{!Label|APIName(yyyy)}
4-digit year
2023
FORMAT SPECIFIER
FIELD TYPE
example
{! Tag | API name(C4)}
MOTTO
123,45€
{! Tag | API name(D)}
Optional: precision specifier
{! Tag | API name(D6)}
DECIMAL
1234
-001234
{! Tag | API name(F)}
Optional: precision specifier
{! Tag | API name(F4)}
FIXED POINT
1234.56
1234,5600
{! Tag | API name(P)}
Optional: precision specifier
{! Tag | API name(P4)}
PERCENTAGE
100.00%
-39.7%
{! Tag | API name(N)}
Optional: desired number of decimals
{! Tag | API name(N3)}
NUMBER
1.234567
1,234
For more information, see the following article: https://learn.microsoft.com/fr-fr/dotnet/standard/base-types/standard-date-and-time-format-strings
Make a product subtotal or simply count the number of products
⚠️ The use of extensions requires being on a version of the package later than version 1.7. Please update the package via the AppExchange as required.
Add up the amounts of the same child object, a group or even hidden information and combine multi-currencies. This way, avoid formula-type fields in Salesforce and easily display subtotals.
Word configuration vs generation result
Cumulate the records of the child object to show the number of rows in a table or that meet a criterion entered in Salesforce.
Add up the amounts of the same child object, a group or even hidden information and combine multi-currencies. This way, avoid formula-type fields in Salesforce and easily display subtotals.
By default, the Salesforce layout is applied to the content of a rich text field placed in a Word document at generation. Add one or more tag extensions to change these settings.
To apply the format applied to the tag in the Word template instead of the format used in the Salesforce field, you will need to use a tag extension to allow you to choose exactly the right format.
There are 5 types of formats that can be modified:
“f” for “font” = police
“s” for “size” = size
“c” for color = color
“t” for “type form” = character shape,
“i” for “indentation” = indentation
Make sure to display the image exactly the way you want it
It is possible to display dynamic images when generating a document. Images can be stored directly in fields such as rich text boxes or URLs.
However, we recommend storing the image as a Salesforce file and then storing the Content Version ID on the record
Choose the number of characters in a field
The “Partial Display” feature will be very useful for truncating a text field.
We will use the tag {!obj|field (0.2)} = to return 5A and the tag {!obj|field (2, 3)} To return 123