[CoE Starter Kit - BUG] Environment Capacity capture dates are off by one day

PPCan commented 2 days ago

Does this bug already exist in our backlog?

[x] I have checked and confirm this is a new bug.

Describe the issue

Not sure what's going on, but it looks like the modified date is AFTER the capacity updated on date. Is this supposed to be the way it works?

We are taking snap shots of the environment capacity data to create a forecasting report and the dates not matching is throwing off the report.

It looks like the dates started to be different around August 4th...

Any thoughts..?

Expected Behavior

Dates for modified and capacity updated should match.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.43

What app or flow are you having the issue with?

Environment Capacity from Inventory Run

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

Jenefer-Monroe commented 1 day ago

We get the value to put in the update field from the Power Platform for Admin connector's List Environments as Admin action. See List Environments as Admin

We do this in the CLEANUP - Admin | Sync Template v4 (Other Objects) flow. It looks like it returns UTC time per the format "updatedOn": "2024-10-26T23:20:03Z"

Whereas both Capacity Updated On and Modified On fields from the Environment Capacity custom table are set to show Local Time.

So I think you should be able to extract or infer the UTC version of the time in your custom flows. Hope that helps.

PPCan commented 1 day ago

Ok. If I understand this properly, the 'capacity updated' timestamp is Zulu and is not adjusted for EST. Modified is using EST.

microsoft / coe-starter-kit