Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Feature: Include Response Headers for Open API responses #9986

Open
markwallace-microsoft opened this issue Dec 16, 2024 · 0 comments
Open

New Feature: Include Response Headers for Open API responses #9986

markwallace-microsoft opened this issue Dec 16, 2024 · 0 comments
Assignees
@SergeyMenshykh
Labels
openapi Issues related to the OpenAPI function importer sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)

Comments

@markwallace-microsoft
Copy link
Member

name: Include Response Headers for Open API responses

In case of CREATE operation in dataverse, the response is 204 without a body, but the newly created record id is returned in a header named OData-EntityId.
THere is currently no way to get this header value from a RestApiOperationResponse
@markwallace-microsoft markwallace-microsoft added openapi Issues related to the OpenAPI function importer triage labels Dec 16, 2024
@markwallace-microsoft markwallace-microsoft moved this to Sprint: Planned in Semantic Kernel Dec 16, 2024
@evchaki evchaki added the sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SergeyMenshykh SergeyMenshykh

Labels
openapi Issues related to the OpenAPI function importer sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Projects
Semantic Kernel
Status: Sprint: Planned
Milestone
No milestone
Development

No branches or pull requests
3 participants
@evchaki @SergeyMenshykh @markwallace-microsoft