Please sort ASAP!!

Okay honestly, please do something about this

Full written month format should be included. E.g. 14th December, 2022.

This seems like a simple feature to implement. I hope it comes soon.

Critical for my customer working within HubSpot since date variable does not sync up properly between HSpot & PDoc.

When changing the Default date format under workspace settings, it should influence the system variables (document created date) in the templates/ documents. At the moment the system variables are in American format (Month DD, Year) and there should be the option to have (DD Month Year).

Ability to change the format of Date values that are being pulled into the templates via the SF variables

change the format of the date when document creation is started through hubspot into pandadoc

Within HubSpot Line Items, the standard property "Start Date" date format is not converting from HubSpot to PandaDoc in the date format I have set in my PandaDoc profile settings. For example, the Start Date that appears on my template is YYYY/DD/MM but the date format I have set in my PandaDoc profile setting (MM/DD/YYYY). All other date formats convert properly but this does not and seems like it would be a simple fix so that it converts as expected.

Support told me that I would need to create a text property and then a workflow in order to make the data appear as expected on my template. This seems very impractical when there just needs to be a simple date conversion applied to the Line Items standard property "Start Date".

Having the month of June appear as Jun in a document leads everyone to assume its a typo. Frankly I'm shocked this is like this. Even your roadmap date for this request is December 02, 2021.

It is important that different formats are available, as if companies target different markets this differs. Support of different languages would be ideal but a simple date formatting with numbers is simpler and solves the problem. having the DD-MM-YYYY and MM-DD-YYYY would be enough for now. But this is critical, because the variable becomes unusable for non english speaking clients.

The month should be spelled out, not abbreviated when using the [Document.CreateDate] field. Abbreviations do not give a professional appearance. Please review and change.

This is so needed! I am having to create extra fields in the CRM to produce text versions of the date and merge them into the PandaDoc templates.
In case anyone should need it, here is an example Salesforce formula that takes a custom date/time field and converts it from"23/11/2021" format to "23rd November 2021" - You can substitute Date_Today__c for "CreatedDate" or even "Now()" for instance.

(TEXT(DAY(Date_Today__c)))
+(CASE(DAY(Date_Today__c),
1, "st",
2, "nd",
3, "rd",
21, "st",
22, "nd",
23, "rd",
31, "st",
"th"
))

+" "+
CASE(
MONTH(Date_Today__c),
1, "January",
2, "February",
3, "March",
4, "April",
5, "May",
6, "June",
7, "July",
8, "August",
9, "September",
10, "October",
11, "November",
12, "December",
"None")

+" "+TEXT(YEAR(Date_Today__c))

This would be a great feature to have! Also for imported date fields from CRMs (Hubspot / Sales Force). It would be great to be able to format these to fit specific offers or different locales (countries). We have different templates for different countries - it would be great if we could set a fitting format in the template for each date field.

Yes, when we have a specific date format, it makes perfect sense that tokens has the same values, since we i.e. use PandaDoc to Automate Document creation, and we now have different formats!

Much appreciated

Please attend to this one!!! ‼️

The document creation date field is available only in the US date format while all the other fields are available on other format such as DD/MM/YYY or YYYY/MM/DD.....this idea will make the creation date also available in any date format ( which is already available for all other fields)

It looks like this date issue should be brought to the top of the "development teams" list. This is such an important field for our clients to be able to view properly. Having the year first is way too confusing for some people. When can we expect a fix? We shouldn't have to wait for a certain amount of votes as this should have been an option from the beginning. Other programs seem to be able to handle it.

Variable Date Fields such as ​[Document.CreateDate] should have the option to select what date format is most appropriate.

Instead of "Jun 10, 2021", It would be great to read as the full month - "June 10, 2021".

Would definitely be in favor of the MM/DD/YYYY option.