Forum Discussion
Liquid Date Formatting for API-Triggered Properties
I'm trying to format the date and time on our transactional appt confirmation emails. I found a formula that worked perfectly when I used a date field from Braze, but when I plug this same formula in...
Arsoprovided some great feedback already, but here are some thoughts in slightly different color:
- I have a feeling that when the date value is stored in Braze as a Custom Attribute, Braze is a bit more flexible with different date formats and is recognizing your current date format as a Date datatype
- But when you’re inserting data directly as an API trigger property, it’s not getting the same flexible treatment as your Custom Attributes. And Braze does recommend iso8601 (YYYY-MM-DD…) format for date variables.
Your Liquid looks fine and should treat both outcomes the same, but I always like to see how the original value is rendered when debugging.
So just rendering your CA and your API trigger properties with any date filter applied would be a great first step!
And we would suggest altering the way the data comes into Braze instead of using Liquid to manipulate the date format… but if you do go the latter route, Arso looks like he did the hard part for us already!
