Showing results for 
Search instead for 
Did you mean: 
Not applicable

CosmosDB Query Documents Returns Incorrect ID (drops trailing 0s)

Will try to keep this as succinct as possible then will respond to any replies asking for more:


Using Cosmos DB query (V4 & V3) widget to query documents so I can perform actions against those we need to, simple enough.























Now, that seems fine and all, until I actually LOOK UP that ID:


It's dropping the trailing 0s.


Now, I understood this to be a string field and would not expect any transformation on my id.


This ONLY happens if the ID has trailing 0s before the Z, and will happen if I do not put any predicates in my query.


Seems like a pretty substantial issue if you ask me. Please let me know if anyone would like to see further information, happy to share because I'd be even happier if this got resolved.

Not applicable

I'm able to pick the ID back up and transform it back to a standard date format

yyyy-MM-ddTHH:mm:ss.fffZ, but the fact that it manipulates my ID field in my return is just wild. 

Helpful resources

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

User Group Leader Meeting January 768x460.png

Calling all User Group Leaders!

Don't miss the User Group Leader meetings on January, 24th & 25th, 2022.

Users online (1,608)