Wrong Date Picker date format

(3) Share

Report

Posted on by kamputyje

This is a new problem that I haven't encountered before. When I open my app for editing, the default version is always 3.24122.12. With this version, Datecardvalue/DatePicker fields have a date format of "Fri, Dec 27, 2024" and are completely unresponsive to format changes to others. If I set the previous version, it shows my chosen date format (while I'm in Edit state). But opening the app after "Publish" shows the wrong format again (both in test and production environments). What's going on? :O

Categories:

Building Power Apps

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

cha_cha 4,932 Moderator on at

Like (1)

Report

This version has been reported have a number of bugs in the forum. It's better to stay in the old version til a more stable version is released.

Was this reply helpful? Yes No
scalca 243 Moderator on at

Like (0)

Report

does this issue happen on modern or classic control?
can you pls share your formula

Was this reply helpful? Yes No
kamputyje 10 on at

Like (0)

Report

@scalca
I checked, yes - it is modern controls. There are many of them, their formulas are different, but even with the simplest today(), the situation is the same (it does not respond to the selection of the format at all). Also text(today(), "yyyy") shows the same nonsense even though it shows "2024" in the old date picker.
So I realized that the modern control date format option doesn't work in 3.24122.12 version...

Was this reply helpful? Yes No
kamputyje 10 on at

Like (0)

Report

@cha_cha
Thanks, this is really the only solution. Just yesterday I was stuck in that awful 3.24122.12 version. It was not possible to save with the previous version of the app. Today, at least in this place, everything is in order.

Was this reply helpful? Yes No
Suggested answer

VASANTH KUMAR BALMADI 266 on at

Like (0)

Report
Possible Causes and Solutions

1. App Versioning and Caching

Cause: PowerApps has a versioning system, and the published version may not reflect the changes made in the editor immediately. Sometimes, changes to the app, like date format settings, are cached or not fully synchronized between the editing environment and the published version.

Solution:

Clear the app cache: Try clearing the cache for PowerApps (or use a private/incognito browser window to test) to ensure you’re seeing the latest version after publishing.

Re-publish: After making changes, ensure you are republishing the app. Sometimes, you might see an old version if the republish process doesn't fully update.

Publish a new version: Make sure that the published version reflects the most recent changes. Sometimes the version number in PowerApps may show an old version even after changes are made.

2. Date Formatting in PowerApps

Cause: The DatePicker control in PowerApps might be defaulting to a specific date format based on your locale settings. When editing the app, it might apply your chosen format, but when the app is published, it defaults to a system format (e.g., "Fri, Dec 27, 2024") which might not be the one you expect.

Solution:

Use Text function to format the date explicitly. Instead of relying on the default format of the DatePicker, try setting the Text property of the DatePicker to a specific format like:

Text(DatePicker.SelectedDate, "[$-en-US]yyyy-mm-dd")

This ensures the format is consistent and not affected by the system's default format settings.

3. Locale Settings

Cause: PowerApps apps are sensitive to the locale of the environment (e.g., the region settings for the environment in which the app is published). Different locales might use different date formats (e.g., MM/DD/YYYY vs DD/MM/YYYY), which can lead to inconsistent formatting behavior.

Solution:

Set the locale explicitly in your app to standardize the date format:

Set(varLocale, "en-US")

You can then use Text(DatePicker.SelectedDate, varLocale & "yyyy-mm-dd") to apply a consistent date format based on your preferred locale.

Ensure that the environment settings for your PowerApps environment are consistent with the intended locale.

4. Update or Reset Datepicker Format Settings

Cause: There may be an internal bug or issue with the version you're using (e.g., version 3.24122.12) where datepicker settings are not being applied correctly after publishing.

Solution:

Ensure that your PowerApps and PowerApps Studio versions are up to date. If you're using an older version of PowerApps, there might be a bug affecting the date picker formatting that was fixed in later releases.

Try removing and re-adding the DatePicker control to reset its properties.

5. Environment-Specific Behavior

Cause: Sometimes, different environments (Test vs Production) may have slight configuration differences that affect how certain controls behave, especially when it comes to date formatting.

Solution:

Verify if any environment-specific settings (like language/region settings) are influencing the date picker.

Test the app behavior in different environments (e.g., both Test and Production) to see if the issue is environment-dependent.

Was this reply helpful? Yes No
WarrenBelz 153,084 Most Valuable Professional on at

Like (0)

Report

@VASANTH KUMAR BALMADI

If you are going to copy and paste from Chat GPT, please state this at the top of the response so users can make an informed decision on the possible relevancy.

Was this reply helpful? Yes No
Suggested answer

dmac92 3 on at

Like (0)

Report

Not sure if the latest authoring versions have fully fixed this, but I did come across a reddit post saying the format property of modern date pickers do support string formats.

I changed 'DatePickerCanvas.Format'.Short to "mm/dd/yyyy" and everything seems to format that way!

Was this reply helpful? Yes No