[CoE Starter Kit - BUG] identifying pending suspension flows as having their metadata changed when they havent really due to date difference between dataverse connector and flow connector

[Jenefer-Monroe]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

Admin | Sync Template v4 (Flows) flow is identifying pending suspension flows as having their metadata changed when they havent really due to date difference between dataverse connector and flow connector

[
{
"FlowID": "1a1aaa11-1a1a-1111-aaaa-ab21ab121aaa",
"FPS_On": "2023-10-31T10:17:07.996529Z",
"FPS_PAExcluded": null,
"FPS_Reason": "NonCompliantServicePrincipalFlow"
}
]

[
{
"FlowID": "1a1aaa11-1a1a-1111-aaaa-ab21ab121aaa",
"FPS_On": "2023-10-31T10:17:07Z",
"FPS_PAExcluded": null,
"FPS_Reason": "NonCompliantServicePrincipalFlow"
}
]

Expected Behavior

coalesce(split(item()?['properties/estimatedSuspensionData/time'], 'T')[0], null)

coalesce(split(item()?['admin_flowpendingsuspensionon'], 'T')[0], null)

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.16

What app or flow are you having the issue with?

Admin | Sync Template v4 (Flows)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

AB#796

[CoEStarterKitBot]

@Jenefer-Monroe This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.