TimeZones and Date Picker not displaying the correct Date

[JimmyKhan2021]

I have a Power BI Report connected to a Canvas Power App . There is a DATE data type for a field called Purchase Date in the Power App Form . The Purchase date in Power BI Report is 14th Nov 2021 , The Date displayed in the connected Power App form is 11/13/2021 9:00 PM. 

The time zone is Moscow which is UTC + 3hrs . Why cannot the DATE PICKER display the date correctly ? 

Only way I have found is converting it to a TEXT Field and displaying in a label but this means I cannot use the DATE Picker Visual in Power Apps .  I have tried all the - or + timezone() Date Add suggestions, and feeding  a TEXT value of the DATE from the Power BI to the DATE PICKER which  converts it to strange date in 2022, which I don't understand . 

Some stuff I have tried and failed with : 

TEXT ( DateAdd(DateTimeValue(First([@PowerBIIntegration].Data).purchasedate) ,-TimeZoneOffset(Now()),Minutes),"[$-en-US]dd/mm/yyyy")

Text( First([@PowerBIIntegration].Data).purchasedate , "[$-en-US] dd/mm/yyyy")

Text(DateValue(Text(First([@PowerBIIntegration].Data).purchasedate )) ,
DateTimeFormat.ShortDate )

I have played about with the format property , language property  the local and utc properties and no success . 

This seems like some very basic functionality for operating Power Apps in different timezones that is seriously lacking and I am really concerned that I cannot find a solution, especially after investing so much time into this . 

Do you have any suggestions I can try to make the Date Picker display the DATE coming from Power BI correctly if I am a Power APP User in a different Time Zone other than UTC ? Moscow , Australia , Germany etc . 

[RandyHayes]

@JimmyKhan2021 

Couple things...

1) The strange date you saw was probably Jan 11 2022.  This is all due to your regional date time format.  If a date of "mm/dd/yyyy" is 11/13/2021 and your region is "dd/mm/yyyy", then it will assume the 13th month of the year, which would be Jan of the next year and the 11th as the day.

2) Your datepicker is concerned only with the date...not the time.  From what I am reading in your post, if something happens at 9 PM in UTC +3  then in any other time zone, you want it to just display the date recorded and not to take into account the time/timezone.

If that is the case, then set your DefaultDate property  to: DateValue(Text(First([@PowerBIIntegration].Data).purchasedate))

In other words, drop the final conversion to text that you had in one of your attempts.

I hope this is helpful for you.

[JimmyKhan2021]

Thank you Randy for replying and the explanation of the strange 2022 date.

I have tried your suggestion and it works in the Power Apps Studio, but when I use the Power App in the Power BI Service through the Power App, unfortunately it gives me the 13th November 2021 instead of the 14th November 2021 . The day before . 

My understanding is that Power App communicates in UTC with other connectors such as Power BI and SharePoint, so if you are using the App in Moscow , 3 hours ahead of UTC it will convert even "dates" fields and add internally a time component and push the date to the UTC value and surface that in Power App . So my purchase date of 14th November 2021 becomes internally in the Power App  a date of the 14th November 2021 000000 and then when surfacing that "Date" in the Date Picker it says I must make automatically display it in UTC , so it makes it 13th November at 9pm and in the date picker you see 13th November 2021 .  This is what I am seeing and it is frankly bizzare why you turn off this behavior in the Power App . This Power App reads from Power BI and then writes to a SharePoint List , so it this a problem unique to these kinds of Power Apps . 

Is there another way round this as I am getting more and more desperate by the passing day ?

[JimmyKhan2021]

If I change this setting to UTC it goes to the 12th November 2021 

[RandyHayes]

@JimmyKhan2021 

You really only want to make sure your date picker is getting JUST a date - no time.

I am not sure if the date coming from the PowerBI part has timezone information, but it sounds like it does.

Some things to try (sorry just winging a couple things without knowing the exact data coming in):

DateValue(Text(DateAdd(First([@PowerBIIntegration].Data).purchasedate, TimeZoneOffset(), Minutes)))

Or

With({_dt: First([@PowerBIIntegration].Data).purchasedate},
    DateValue(Text(DateAdd(_dt, TimeZoneOffset(_dt), Minutes)))
)

Or

With({_dt: First([@PowerBIIntegration].Data).purchasedate},
    DateValue(Text(DateAdd(_dt, -TimeZoneOffset(_dt), Minutes)))
)

See if any of those hit the mark.  Make sure all the rest of your date picker is set to normal...I know you've been toying with a few of the properties.

[JimmyKhan2021]

Interestingly the Field from Power BI that I believe to be a DATE Field has an issue with these formula. 

Maybe it the type of date I am bringing in from Power BI ? How can this not be a valid date value ?