Open Dental Forum

Good Day,

I have an issue when updating date fields using PatFields PUT endpoint. The display format of the updated field on Open Dental changes from "dd/MM/yyyy" (eg. 03/04/2025) to "yyyy-MM-dd" (eg. 2025-03-04).
Thank you.

dr4com4lfoy wrote: ↑

Wed Apr 30, 2025 12:23 am

Good Day,

I have an issue when updating date fields using PatFields PUT endpoint. The display format of the updated field on Open Dental changes from "dd/MM/yyyy" (eg. 03/04/2025) to "yyyy-MM-dd" (eg. 2025-03-04).

change-1.PNG

change-2.PNG

Thank you.

Good morning dr4com4lfoy,

Sounds like Open Dental may not localize patfield date formats when loading from the database. The API team will look into this behavior and report back here.

Thanks!

justine wrote: ↑

Wed Apr 30, 2025 10:55 am

Good morning dr4com4lfoy,

Sounds like Open Dental may not localize patfield date formats when loading from the database. The API team will look into this behavior and report back here.

Thanks!

Good Day,

Any update to my concern?

Thank you for all you guys do.

dr4com4lfoy wrote: ↑

Thu May 15, 2025 7:02 pm

justine wrote: ↑

Wed Apr 30, 2025 10:55 am

Good morning dr4com4lfoy,

Sounds like Open Dental may not localize patfield date formats when loading from the database. The API team will look into this behavior and report back here.

Thanks!

Good Day,

Any update to my concern?

Thank you for all you guys do.

Hello dr4com4lfoy,

The API requires date values for PatFields to be submitted in yyyy-MM-dd format; a universal unambiguous format that's consistent across all regions. Since the API is used globally, we avoid localizing date input/output to prevent confusion.

When entering dates through the Open Dental UI, the software may reformat the date based on the local machine’s CultureInfo, but that doesn’t currently happen for API-entered values.

The data is still valid and saved correctly. It's just displayed in a consistent, non-localized format.

Thanks!