I have a SQL DateTimeOffset field (yes, I converted them to this handy international SQL datatype as suggested for Power Apps in Working with date/time values and SQL Server | Microsoft Power Apps).
We need to show times without their dates, eg "17:45", however for some reason the Power Apps Format on Text Input control of DateTimeFormat.ShortTime24 still shows the ugly underlying long datetime, like "30/12/1899 17:45". This is nasty and very confusing to users. I thought the whole point of ShortTime24 would be exactly what is says. There's no good in using the Time() function because that's just for converting Text, whereas we do have the correct underlying datatype (so it causes an error).
Naturally, this applied to the standard SQL DateTime datatype as well as newer DateTimeOffset, so no fix there.
Is this a bug / unimplemented functionality, or am I missing something? What is the best practice for showing and editing short Times which can be patched back to the database?