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

error | Modelerfour/IncompatibleRequestBodies | Operation 'Imports/PostImportInGroup' content types [json, multipart] have the same body schema but cannot be used together #4956

Open
KotanaSai21 opened this issue Apr 22, 2024 · 0 comments
Open

error | Modelerfour/IncompatibleRequestBodies | Operation 'Imports/PostImportInGroup' content types [json, multipart] have the same body schema but cannot be used together #4956

KotanaSai21 opened this issue Apr 22, 2024 · 0 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@KotanaSai21
Copy link

We're facing the below error with our swagger file while including multipart/form-data. Check my swagger file here.
image

We want to include both content type application/json & multipart/form-data to our request body header. But after migrating to Azure Core and generating files using autorest v3 we're facing the above error.

Could you please help us to resolve this issue?
@KotanaSai21 KotanaSai21 added the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label Apr 22, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KotanaSai21