Durable Functions HTTP API: Response structure mismatch List entities vs Get entity #3243
Unanswered
jaliyaudagedara
asked this question in
Q&A
Replies: 1 comment
-
|
@lilyjma FYI |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently,
List entities:
Say, we are passing
fetchState=truein the QueryString.The response looks like something like below:
[ { "entityId": { "name": "someEntityName", "key": "0002f3c57ec845cea5096d026cb4f895" }, "lastOperationTime": "2025-10-21T17:34:06.9945586Z", "state": { "prop1": "value1", "prop2": "value2", } }, { "entityId": { "name": "someEntityName", "key": "0004d73c2bdf4e86a4d56c31d222717c" }, "lastOperationTime": "2025-08-21T15:05:26.2092795Z", "state": { "prop1": "value1", "prop2": "value2", } }, .... ]Get entity:
The response looks like something like below,
Note: Only the state being returned.
From the REST perpective, shouldn't this return the entire
Resource,{ "entityId": { "name": "someEntityName", "key": "0004d73c2bdf4e86a4d56c31d222717c" }, "lastOperationTime": "2025-08-21T15:05:26.2092795Z", "state": { "prop1": "value1", "prop2": "value2", } }Beta Was this translation helpful? Give feedback.
All reactions