Wrong datetime format in Dynamic Value in Tool "List all shifts in a team"

(1) Share

Report

Posted on by Louisa#

Hello all,
I am using the "List all shifts in a team" tool from "Shifts for Microsoft Teams" in my Copilot Studio agent. However, the return value provides an excessively large number of files, and I would like to narrow this down using the input parameters startTime and endTime. The only available entity for this purpose is "Date and Time," which must be in the ISO-8601 format (including T and Z). I have explicitly stated this requirement in the description. Unfortunately, it does not work, and I am receiving a 400 error message [Innerer Fehler: Invalid filter clause: An identifier was expected at position 29.

Some ideas, how to solve this?

Best regards

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Romain The Low-Code... 2,575 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

hello,

i had a very similar problem with date in another tool. What helped me was to force the time zone in the global prompt with a power fx formula, it could help you i hope :)

Was this reply helpful? Yes No
chiaraalina 1,921 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @Louisa#

I had the same problem with that tool. At first I thought it was because I hadn’t provided an end date, but even after adding it, it still didn’t work.

I tried using PowerFx and setting a variable, but nothing helped. I assumed it’s a bug.

The only thing that worked for me was creating my own custom connector for it. But maybe @Romain The Low-Code Bearded Bear can provide more information on his suggestion.

Was this reply helpful? Yes No
Suggested answer

Romain The Low-Code... 2,575 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@chiaraalina hello :) thanks for the tag.

You are totally true i confirm you'r that, to my opinion it's the good option.

My "little "workaround was to use PowerFX to fixe the time zone in the global prompt and adding the date time. But it's a workaround depending on the "understanding" of the prompt.

For production target i recommand like you said and another option :

- put inside a agent flow or power automate the connexion and inside the flow add some "watcher" to correct the format (as i m bad at dev i use "AI Builder prompt" to correct date input (but it's not cost efficient) : sample i make ai builder prompt witch is told and explain the situation and will correct the date input.

- the cost efficient way is like Chiaraalina said : having you'r custom connector with custom code to correct date

if this solve the case please check as verified answer it's important for the community and search engine :)

Was this reply helpful? Yes No
chiaraalina 1,921 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

@Romain The Low-Code Bearded Bear thanks!

@Louisa# If you want to use a custom connector and need help with that, let us know!

Was this reply helpful? Yes No
Louisa# 36 on at

Like (1)

Report
Copy link

Link copied!

@chiaraalina I created an MS-Call for this. The product group says it's a bug and they are working on a permanent fix. However, there is no ETA yet.

Was this reply helpful? Yes No