Power Platform Community Forum Thread Details

IcM Connector 'When incident created' trigger - datetime encoding bug

PROBLEM SUMMARY
The 'When an IcM incident is created' trigger in Power Automate is failing with a BadRequest (HTTP 400) error. The connector internally appends a CreateDate filter clause to track polling state, but generates a malformed datetime literal where the '+' in the UTC timezone offset is replaced with a space, causing IcM's OData endpoint to reject the request.

---

ROOT CAUSE
The connector auto-appends the following clause:
and CreateDate gt datetime'2026-04-07T04:32:16.479 00:00'

The correct format should be:
and CreateDate gt datetime'2026-04-07T04:32:16.479+00:00'

The '+' character (which should be URL-encoded as %2B) is being encoded as %20 (space), resulting in an invalid Edm.DateTime literal that IcM's OData API cannot parse.

---

EVIDENCE
Failing Search URL generated by connector:
https://prod.microsofticm.com/api/user/incidents?$filter=%28OwningTeamId%20eq%20%27SAPTRPINTEGRATIONSERVICES%5CTRPISLiveSite%27%29%20and%20CreateDate%20gt%20datetime%272026-04-07T04%3A32%3A16.479%2000%3A00%27&$top=100

Decoded filter:
(OwningTeamId eq 'SAPTRPINTEGRATIONSERVICES\TRPISLiveSite') and CreateDate gt datetime'2026-04-07T04:32:16.479 00:00'

IcM OData Error:
"Unrecognized 'Edm.DateTime' literal 'datetime'2026-04-07T04:32:16.479 00:00'' at '78'"

---

IMPACT
- Flow: TRP ICM Config Automation Agent (ICMBased_Automated_Config_Management)
- Owning Team: SAPTRPINTEGRATIONSERVICES\TRPISLiveSite
- The flow was working correctly until approximately March 11, 2026
- All IcM incidents created after that date are being missed — no automation is firing
- This appears to be a regression introduced in a connector update between March 11 and April 6, 2026

---

STEPS TO REPRODUCE
1. Create a Power Automate flow with trigger 'When an IcM incident is created'
2. Set filter: OwningTeamId eq 'SAPTRPINTEGRATIONSERVICES\TRPISLiveSite'
3. Set Search Endpoint: Public
4. Save and enable the flow
5. Observe BadRequest 400 error on trigger execution
6. Check the Search incidents URL in the error — note %2000%3A00 instead of %2B00%3A00

---

EXPECTED BEHAVIOR
Connector should generate a valid datetime literal with '+' properly encoded as %2B in the URL:
datetime'2026-04-07T04:32:16.479+00:00'

ACTUAL BEHAVIOR
Connector generates an invalid datetime literal with space instead of '+':
datetime'2026-04-07T04:32:16.479 00:00'

Categories:

Power Apps portals

Hi SN-07040643-0,

This is a connector bug on Microsoft's side — nothing you can fix in the flow itself.

The IcM connector is incorrectly encoding + as a space instead of %2B in the datetime filter it auto-generates. This broke somewhere between March 11 and April 6, 2026.

What to do:

Report it via the Power Automate feedback button (flag icon on the trigger) — reference the exact URL with %2000%3A00 vs expected %2B00%3A00

Open a Microsoft support ticket — you have solid evidence (the decoded URL, the regression date, the OData error). That's everything they need.

As a temporary workaround, try setting the timezone in your filter explicitly to UTC using Z instead of +00:00 — some OData endpoints accept datetime'2026-04-07T04:32:16Z' — but this depends on what IcM accepts.

You can't patch the connector encoding yourself. This needs a fix from Microsoft.

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Just mention @Soufyane and I’ll be happy to assist.

💛 A Like always motivates me to keep contributing!

Quick Links

Subscribe to this forum!