[Silk UI Web] TimeToAmPmText function bug

Forge Component
(89)
Published on 25 Mar by OutSystems R&D
89 votes
Published on 25 Mar by OutSystems R&D

How'd 

the TimeToAmPmText function returns incorrect times between 24hr times of 00:00 - 00:59 and 12:00 - 12:59. 

Example: 

00:32 returns 0:32AM where is should display 12:32 AM 

12:54 returns 0:54PM where is should return 12:54 PM

Cheers

Steve



ouch :/

It's 2019 and this is still is unsolved, and the thing is when you use that output to call AmPmTextToTime it throws an error.

João Almeida wrote:

It's 2019 and this is still is unsolved, and the thing is when you use that output to call AmPmTextToTime it throws an error.


Hi guys,

We'll take a look into both actions to understand what is the error being thrown.

Thank you for reporting this.

Dinis Carvalho wrote:

João Almeida wrote:

It's 2019 and this is still is unsolved, and the thing is when you use that output to call AmPmTextToTime it throws an error.


Hi guys,

We'll take a look into both actions to understand what is the error being thrown.

Thank you for reporting this.

Thanks DInis. Actually AmPmTextToTime is throwing an error as expected, as 0:00 AM it indeed is an invalid time format. The problem is only the TimeToAmPmText side, where the expected output format should be 12:00 AM


Hi guys,

We have already worked on it. Expect it to be fixed in the next release!

Best Regards

Yeah good to see it getting fixed, I had addressed the same thing in early 2017...

https://www.outsystems.com/forums/discussion/21521/ampmtexttotime-works-except-from-1200pm-to-1259pm/

Hello everyone.

The new version of Silk UI Web is released and the fix is now available for both versions 10 and 11 of the platform.


Also as improvements in this version:

  • The Calendar pattern was renamed to DatePicker, for consistency between Silk UI and OutSystems UI


Cheers