Answered

Records showing either correct date or 1-day-wrong date in model driven app.

(1) Share

Report

Posted on by jzimmermancase

367

So I have an app that has student records for the current year and projected into the next year. A flow copies data from the current year into the projection year.

When viewed from the model driven app, the Current Year record shows the correct date, but the Projection Year record shows the date 1 day behind.

All date fields are 'Date Only'.

My timezone is UTC-06:00

I can confirm that the date field in each record contains the same data:

However, the model driven app displays the data wrong in only one of the records:

In Power Automate, my flow is copying the date from the Current to the Projection record. Here are the inputs and outputs of the flow:

Everything looks correct, but the model driven app still shows the date wrong for one of the records.

I can "fix" the problem by setting my Dynamics user preferences to a timezone of GMT-0, but I would rather have a programmatic fix that doesn't involve giving all of my users the wrong timezone.

Any help appreciated.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (14)

Answers (1)

Hamish Sheild 3,005 Most Valuable Professional on at

Like (0)

Report

What user account are you using for the Flow connections to CDS? And what is their Timezone setting? It’s possible that the Flow connection user has their Timezone set to UTC-0.

For future reference, when the date field was created it should have been set as a Date Only type. This avoids this scenario. Typically date fields should be created as Date Only in CDS unless the time component is required. Unfortunately, if you want to change the field to Date Only then you need to create a new field, migrate the data and delete the old field.

Was this reply helpful? Yes No
jzimmermancase 367 on at

Like (0)

Report

As a matter of fact, all of my date fields are Date Only, which makes this problem just that much more bizarre.

Date Only fields don't exclude time data, they just force it to T00:00:00Z, which you can see in the Power Automate output in the screenshots above. As an experiment I used an "add hours" expression and there were no errors, but the time was still T00:00:00Z.

Was this reply helpful? Yes No
Hamish Sheild 3,005 Most Valuable Professional on at

Like (0)

Report

OK, good to see you are using date only fields.

Did you look at the user account that is being used for the CDS connector within the Flow?

Was this reply helpful? Yes No
jzimmermancase 367 on at

Like (0)

Report

My own account is the owner on the flows. Its time zone settings are configured through the Exchange server and synced, as follows:

All of the affected users have their time zones configured as UTC-06:00. This shouldn't matter, because in theory Date Only fields ignore time zone.
Here's another view of the symptom. You can see each student has a 19-20 and a 20-21 record. And you can see the the 20-21 records' dates are all 1 day earlier. They should be the same.

HOWEVER, Power Automate doesn't see this at all--it thinks the dates are the same. Here is the output of a "List Records" step from the same entity. Date fields are in red. This is the same student circled in red above.

Canvas Apps has a different opinion.

Aha! So Power Automate is altering the data based on the owner's (my) timezone. It looks like it's subtracting 5 or 6 hours.

So how do I fix this? Should I make a post in the Power Automate community instead?

Was this reply helpful? Yes No
Nhelgren on at

Like (0)

Report

Have you checked the time zone for the user that is having the issue?

Was this reply helpful? Yes No
jzimmermancase 367 on at

Like (0)

Report

Yes, they are on UTC-06:00 'Central Standard Time'. Everybody is.
On a lark, I tried:
convertTimeZone(triggerOutputs()?['body/case_mostrecentiepmeeting'],'Central Standard Time','UTC')
But this has no effect. Power Automate keeps inputting the date minus 6 hours.
I also tried:
And:
But they both result in:
and
and

Was this reply helpful? Yes No
jzimmermancase 367 on at

Like (1)

Report

I have posted this as a bug report:
https://powerusers.microsoft.com/t5/I-Found-A-Bug/Flow-owner-timezone-incorrectly-affects-Power-Automate-date/td-p/443905

Was this reply helpful? Yes No
Verified answer

jzimmermancase 367 on at

Like (0)

Report

Solution is here.
https://powerusers.microsoft.com/t5/I-Found-A-Bug/Flow-owner-timezone-incorrectly-affects-Power-Automate-date/m-p/454233/highlight/true#M6161

Was this reply helpful? Yes No
micahthobbs 26 on at

Like (8)

Report

Anyone know why I might be getting this Access Denied when following the solution link? Thanks.

Was this reply helpful? Yes No
JPS_PowerApps 6 on at

Like (0)

Report

I was also unable to reach this page. The fix for me on this was going into the column settings in sharepoint, going into advanced settings, and setting the column as timezone independent.

Was this reply helpful? Yes No