Unlocking seamless data integration: Introducing nested schema models

Challenging workaround for working with nesting in a Swagger file

We acknowledged that low-coders are facing a significant challenge when working with nested schema models in the Swagger and XML files used to connect external data sources. Nearly every Swagger file contains a nested data structure. However, the inability to directly select and use these nested models in actions meant that developers had to spend additional time and effort to modify Swagger files or employ workarounds like additional parsing steps (such as using JSONpath or extra action steps).

The first step to unlocking seamless data integration

To address this, we have extended the Data IDE with the possibility to create “has one” and “has many” relations to build a nested schema model structure. As well as the schema model browser with a click-through functionality, allowing users to easily navigate and select nested schema models (i.e., child models within a parent schema) directly within actions. This enhancement is the first step in providing a more intuitive and efficient way to manage complex data structures, making the development process for data sources faster and more straightforward.

Why it matters:

• Improved efficiency: By enabling direct selection of nested schema models in Actions, this feature reduces the need for additional steps and workarounds. Low-coders can now build actions more efficiently, saving time and reducing errors.
• Enhanced flexibility: The ability to work directly with nested schema models in actions input and HTTP steps offers greater flexibility in handling complex data structures. This is particularly valuable for organizations dealing with intricate data sources, such as those using Swagger files.
• Builder impact: This feature eliminates the need to unpack arrays and objects in Actions, leading to a more seamless development experience. The reduced reliance on extra parsing steps (such as JSONpath) also simplifies the overall workflow.

Want to read more about how to create nested schema models? 

Up next

The upcoming months we will be working towards the end goal: seamless integration of a Swagger file that contains a nested structure within a Betty Blocks application. Currently, modifications to the Swagger file in order to connect the data source is one of the most time consuming efforts a low-coder needs to take. With this enhancement, low-coders will have full access to all nested models described in the Swagger file, eliminating the need for manual adjustments and ensuring complete data integration using Swagger files.