AEM forms 6.3 data integration swagger

[#1]

Hi,

I have configured data integration using a swagger (Json) file. In this file the endpoints are defined and also the fields.

This works just fine for fields that are of type string, numeric  However the swagger file I am using describes nested objects E. G.

Object1

     StringField1

     StringField2

     Object2

          StringField3

          StringField4

          StringField5

the fields for object1 are correctly identified by AEM. Object2 and its fields are ignored.

If I restructure the swagger file so they objects are not nested aem processes it correctly :

Object1

    StringField1

    StringField2

Object2

          StringField3

          StringField4

          StringField5

Does AEM support this nested object structure in swagger? If so do you have an example swagger file that demonstrates the correct syntax.

If not, what is the alternative? Add a key to each data structure and link them?

Thanks,

James

[#2 · Accepted solution]

Hi James,

I checked Internally and the parsing API provided by Swagger has a limitation with nested inline objects. Please try to create an inline definition for the nested object Object2 and use $ref to refer to the definition from Object1.

[1] Using $ref | Swagger

[#3]

Many thanks Mayank.

I tried the same thing earlier and it works, good to know it is the recommended approach.

The example I found was in the petstore swagger example:

https://petstore.swagger.io/v2/swagger.json

Search for Category

Thanks,

James

[#4]

Hi James,

Good to know that it's resolved now.