I recently added a temporary workaround for this challenge.
Set up
Set up 4 properties
"Time" - Single-line text property
"Hour" - Number property
"Minute" - Number property
"AM/PM" - Dropdown property with values "AM" and "PM"
Set up 1 workflow
Enrolment criteria (re-enrolment turned on for all)
"Hour" is known
"Minute" is known
"AM/PM" is known
If/Then branch - IF Minute is between 0 and 9, go to branch 1, else go to branch 2.
Branch 1
Action
Set property value for "Time" to "{{ Hour }}:0{{ Minute }}{{ AM/PM }}" using tokens.
Branch 2
Action
Set property value for "Time" to "{{ Hour }}:{{ Minute }}{{ AM/PM }}" using tokens.
Form
Add the hour, minute and AM/PM properties as a row into the form.
Set the hour property to have a limit to the numbers accepted
Minimum 1
Maximum 12
Set the minute property to have a limit to the numbers accepted
Minimum 0
Maximum 59
Set all 3 fields to mandatory
Result
You'll have a form that contains 3 fields for your contacts to fill out the exact time they want, without the need for millions of dropdowns.
8:05AM
12:47PM
Etc
The workflow will combine the values into a single field for you to use.
Branch 1 of the workflow adds a 0 before the minute where it's a single digit number (0-9), otherwise you'd end up with 8:5AM instead of 8:05AM.
Limitations
The resulting time property is single line, which limits any filtering you'd use in numbers, etc. You'd be forced to use value contains "10:" and "AM" to find times for 10am as an example.
There are no filters around time, so you wouldn't be able to look for "Time after 10am" for example
Having 3 fields requires that all the fields are filled in rather than 1. This would force you to make them all mandatory which doesn't always work out in a form where it should be optional.
These limitations are the main reasons I'd still be requesting the property type from Hubspot in the future, but hopefully it helps you all in the meantime.
