Field properties ignored in Azure API Management (APIM) when importing OpenAPI specification with multipart/form-data requests

snehal survase 35

I've encountered an issue where certain field properties, such as "required" and "description," are being ignored in Azure API Management (APIM) when importing an OpenAPI specification that includes endpoints with multipart/form-data requests. Despite ensuring that the OpenAPI specification is correctly defined with the necessary field properties, APIM seems to overlook these properties during the import process.

JananiRamesh-MSFT 27,176 Reputation points

2024-02-28T03:32:39.1566667+00:00

@snehal survase Thanks for reaching out. could you please email your open api spec along with the below details to AzCommunity@microsoft.com we'll get back to you promptly:

• Subject: "Attn: Janani" • Email body: A link to this thread so we can validate and expedite the request
snehal survase 35 Reputation points

2024-02-28T06:27:56.17+00:00

sure!
JananiRamesh-MSFT 27,176 Reputation points

2024-02-29T04:53:19.12+00:00

@snehal survase I have updated my answer please check and let me know incase of further queries, I would be happy to assist you.

Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
CJ Grant 15 Reputation points

2024-04-17T08:36:15.75+00:00

Hi,

We are also experiencing the same issue as of today (17th April 2024). Props we have marked as explicitly required are showing on Swagger as required, but APIM document is showing required: False which is untrue.

Is there any known work-around and/or an active fix for this issue?

Thanks.

CJ

Accepted answer

JananiRamesh-MSFT 27,176 Reputation points

2024-02-28T08:10:51.68+00:00

@snehal survase I understand that you are experiencing an issue and I apologize for any inconvenience this may have caused. I have tried to reproduce the issue on my end, and I was able to see the same behavior.

After checking internally, it appears that this is a known issue and a current limitation. Please know that we have already added this to our backlog, and we are working on a solution.

In the meantime, we will update our documentation to reflect this limitation.

If you have any further questions or concerns, please do not hesitate to let me know. I am here to assist you in any way I can.

Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
Please sign in to rate this answer.

1 person found this answer helpful.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

CJ Grant 15 Reputation points

2024-04-17T08:36:58+00:00

Hi,

We are also experiencing the same issue as of today (17th April 2024). Props we have marked as explicitly required are showing on Swagger as required, but APIM document is showing required: False which is untrue.

Is there any known work-around and/or an active fix for this issue?

Thanks.

CJ

Fred Durham 0 Reputation points

2024-09-13T17:42:40.62+00:00

Hello,

Just another request for a workaround for this apparently still unresolved issue -- anyone had any success?

Thank you.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Field properties ignored in Azure API Management (APIM) when importing OpenAPI specification with multipart/form-data requests

0 additional answers

Your answer