Here we define what form the expected Content will have using a sample. While on the right side we have the Preview of the Content structure for easier overview of the expected data.

Additionally we have the Root schema node field that lets us simplify the sample Content structure by sinking 1 level deeper using the node that’s a level above the data we specifically need.

This same screen will await you for both import and export data types. (with only possible differences being lack of a dynamic url component or there being no pagination in case we are sending data from SyncSpider)

Having written up the sample Content we want to send or receive we click Confirm Changes and the sample gets verified as correct or invalid in the Preview.

Once it is correct the Confirm Changes button switches to a Generate Schema button.

We click Generate Schema and in the background our app derives the expected fields from the sample Content.

Now the Schema appears on the bottom of the screen under Content & json Preview , as shown in this example.

For this validated content:

We get this schema:

We can notice that fields that belong to a complex field have an indent.

At the bottom we have an ADD FIELD button that will add a field to the top level of the schema while the the blue circle with a + on the left of the field data type will do the same for that particular complex field.

At the far right side of the schema each field has 2 checkbox's that allow you to mark it as required and as having multiple value(as some systems require).

The supported data types are: bool, date, number, text, options, collection, complex and hierarchy.

Back to Manual Overview

Did this answer your question?