May I also add my vote to this change?

I am working with many Swagger specifications across Microsoft Azure services and most of them use recursive structures.

The absence of a solution to meet the full Swagger standard is creating a large issue now that I am faced with coding all the return transformations from JSON to structures.  This will not only have a major effect on development times but also create a maintenance burden, as Microsoft is creating updates to their REST APIs apace, especially in Cognitive Services.

I understand this is an outstanding issue since has been reported elsewhere in early 2018, so the community has been waiting nearly three years for a solution.

Would be grateful if you would prioritise this "idea" and help us loyal developers deliver on the promise of Outsystems low-code.

Many thanks

Marc

4 years later and we are still unable to import recursive nested lists. There is a clear use-case for it. afaik, every programming language supports it, except outsystems.

That can be useful and a must-have implementation.

Hi,

Indeed this is a very important integration requirement.

All over Azure integration APIs we can find nested recursive JSON and, most important, the OpenAPI protocol allows that to exist. So if OutSystems wants to be compliant with OpenAPI to allows REST API integrations, it needs to adapt to the specifications.

Follows an example of a current important API that is not possible to integration 100% as documented:

- Azure OpenAI Services (https://learn.microsoft.com/en-us/azure/ai-services/openai/reference?view=azure-dotnet-preview)

> https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/AzureOpenAI/inference/preview/2025-01-01-preview/inference.json

If we try to import the API using multiple methods feature, it will import but it will throw errors because of the nested recursive structures.