Would be awesome if it was possible to add a dynamic content field where as a user i'd have the ability to select a date & time from a calendar selector or dropdown menus and that would outpout a date of the following format:
{day} (in relative format, i.e, tomorrow, Monday, Tuesday etc..) at {time} (example: 6pm)
This is the date that will be rendered: {dateset=day&"/"&month&"/"&year}{=dateset}
{endnote: trim=right}
{=catch({time: {=format}; at={=dateset}; pattern=D/M/YYYY}, {time: {=format}})}{formtoggle: default=no} at {formtext: name=hours; default=02; cols=2}:{formtext: name=minutes; default=00; cols=2} UTC{endformtoggle}{=relativeDay}{note} (tick the box to show and modify the time){endnote}
Thanks for the response. Seems really cool but I was actually looking for a way to avoid inputting or choosing the dates individually, but rather use a calendar selection and output in human language, I guess it's a bit of an advanced feature for this tool.
It's something we've thought about in the past. But it's difficult to define the feature set for it.
In terms of date/time pickers there are so many different options people might want to set (max date, min date, precision (e.g. resolution of a day, hour, minute, month, etc...), valid dates of the week, point-select/range-select, etc...).
It's hard to say what the right feature set would be that would meet most use cases but not be overwhelming.
I've been mulling this over. With the addition of the {time} command's at setting in February (February Development Update), I think this makes sense to add now.
What do people think of this syntax and feature set?
Any references to the formdate's value in formulas will always use YYYY-MM-DD format. You can use a {time} command with at to transform it to something else in formulas.
Also if you don't provide the custom field formatter, the output will be in YYYY-MM-DD format in the final insertion.
'The first approach made formatting the selected date (probably an incredibly common flow) too difficult, so I am tweaking the prototype to require an explicit date format like the {time} command has
IMPORTANT: The following snippet contains experimental features that have not launched; may be changed before launched; or may not be launch.
Basic date field:
{formdate: MMM DD, YYYY}
(Note that on insertion the format "MMM DD, YYYY" will be used. In the form preview though a locale specific entry method will be used and not the specified format)
Say I input a start date. I want to generate the date for 4 weeks, 6 weeks, and 8 weeks after the start date. How would you modify the code {dateset=day&"/"&month&"/"&year}{=dateset} to make this happen? I've tried the shift function as you can do with "time" but I got an error.