Schemas

A schema is the collection which contains everything about your use-case. The schema will contain information about the selected database, module, user groups and the configuration of the structure of the write-back table. Whenever you create a new schema you have to choose one of our modules first. Depending on the selected module the setup of your schema will be different.

Create a new schema

Below you will find the steps to create a new schema. In this example we create a schema with the DATA HELPER module. Click on the first image and a slideshow will show up. use your right arrow to see the next image, use your left arrow to see the previous image.

Below you see an animated gif that illustrates the entire process of creating a new schema. At the end of the animation it also shows how to edit an existing field, just by opening the schema, select the field you want to change and save your changes. The fields available to add to your form are listed below.

• Single Line Text

• Paragraph Text

• Number

• Boolean (Yes/No)

• Dropdown Select

• Date/Datetime

Create schema based on an existing schema

For a data correction schema it is possible to connect to a database table that already exists in your database. The only requirement is that the table has ONE primary key. (Compound keys are not allowed)

To create a schema from an existing table follow these steps:

1. Create new schema

2. Select Data correction module

3. Select Use existing schema

4. Select the connection which connects to the database where the table is located

5. A list of all tables will be presented, Select your table.

6. The new schema wizard will show with all detected columns matched to the field types that WriteBackExtreme uses.

For best compatibility make sure the ID column of the table is a UUID column for example VARCHAR(36). An example statement for a table could look like:

create or replace MY_TABLE( ID VARCHAR(36) NOT NULL, COLUMN_1 VARCHAR(16777216), constraint MY_TABLE_ID primary key (ID) );

When the management console shows an error about a missing primary key, the best way to verify this is by getting the DDL statement or Create table statement from a third party database management tool like DBeaver. This is the easiest way since every database has it's own way of retrieving the primary key information.

This Create schema from existing schema feature can be disabled by an administrator via the advanced settings page.

When there is an error in retrieving the tables or the details of a table, the error log will probably show the true cause. Go to Info & license -> Click on system logs and click the laravel log of today to see the details of the error.