Jun 11

Feature Request: Date Formatting Support for Calculated Fields

ProblemCurrently, calculated fields can concatenate text and dates, but dates are always displayed in their default format (e.g., 2026-06-11 or 11/06/2026).For users building expense trackers, finance logs, journals, habit trackers, and CRM systems, the default date format is often difficult to read and not suitable for generating human-friendly labels.Example:Date of spending: 2026-06-11Generated field:2026-06-11 TeaPreferred output:11 June Teaor11 Jun TeaorJune 11 - TeaProposed SolutionAdd a date formatting function for calculated fields.Example:FORMAT_DATE(Date of spending, "DD MMM")Output:11 JunExample:FORMAT_DATE(Date of spending, "DD MMM YYYY")Output:11 Jun 2026Example:FORMAT_DATE(Date of spending, "MMMM DD")Output:June 11Suggested Format TokensDD → 11D → 11MM → 06MMM → JunMMMM → JuneYY → 26YYYY → 2026Real-World Use CasesExpense trackers11 Jun Tea12 Jun Lunch13 Jun TransportHabit trackers11 Jun Workout12 Jun ReadingCRM systems11 Jun Follow-up15 Jun Client CallDaily journals11 Jun Reflection12 Jun NotesBenefitsBetter readabilityMore professional-looking generated fieldsReduced need for external processingEnables users to create meaningful dynamic labels directly inside Tally formsImproves usability for finance, productivity, and database-style workflowsThis feature would significantly improve the flexibility of calculated fields and allow users to create cleaner, human-readable records without relying on external tools.

Pending