Custom DB

Custom DB allows you to prefill your own internal data into your NestForms responses.

We have many clients using this feature in many different ways. As an example, consider product catalogues, visiting locations that requires extra associated data, regular site visits, linking inventory with QR codes, recording timesheets with QR codes etc.

To get started, you can import an Excel document into NestForms Custom DB. Then choose which columns to show for each form component, when using the Form builder.

We currently support a custom DB containing the following components:

• Dropdown
• Text field
• Number
• Barcode & QR code

You can add/edit/delete rows directly in NestForms. However, you will need to import your first set of data via the Excel file to set the initial structure - see the import process below.

You can also use search to filter the results you are looking for.

You can start on the following URL: https://www.nestforms.com/customdb

First you need to import an Excel document, we also support a range of file types that can be imported, including xls, xlsx, csv and others.

Then you can choose to import into a new or existing table.

The import allows you to apply some magic within the fields you have in the document. You can choose a field as a link to your relations, so the group (row) is linked to the members specified in that field (if they are an active relation).

The system checks the field special values before you import the document, so you can correct any issues if they arise.

After you import your data, you can continue editing your form.

When you have set Member Reference Codes for your relations, you can then apply this code into a column within your Custom DB import file. And if you select the column type Member Reference Code, then each row will be assigned to a specific relation based on the code in the Excel sheet you are importing. This can be useful while using NestForms as a Quality Control checklist app where you have many people inspecting the same products at different locations.

On the form builder, the dropdowns will now have a new checkbox, Custom DB, which when checked, will show the Custom DB dropdown which allows you to select which columns should appear in the form field.

Don't forget to share the form with all responders collecting data. If you have any members selected within the Custom DB, but not in the form share, a warning message will be displayed.

In the app, you will have a new menu item on the left Search Custom DB, which will show you the master groups for each form you are assigned to (the owners will see all of their data). When you choose a group and create a response, the data will be prefilled into it.

The data can also be prefilled using the standard form filling method, so after you open a new response, the dropdown (radio or checkbox) will have the options available and will work the same way as on the Search page.

You can also choose the item GPS position - this means that when using the app the location will be displayed on the map within the Custom DB page.

1) Custom DB rows are shared with all your colleagues (that have the form shared with them) They will receive all Custom DB rows and they will be able to start a response based on the Custom DB data.

2) Custom DB rows are specific to the relation - each colleague will receive only rows that are specifically linked to them. If you login to the app with the master account details, you will see all the rows for testing purposes.

There is a checkbox we call Keep Options which is available for single answer, multiple answer and dropdown component types linked to your Custom DB.

When the keep option is ticked, it means that when a responder is filling in a response, options listed within the component will be displayed.

The main use would be when you have a custom DB row, but in some answers you need to select from a specific set of values.

The big advantage when using Keep Options is that you can also assign Skip logic to these options and hide other questions that are no longer needed. So in this way you can specify which questions are to be selected for the specific custom DB rows.

To use a client scenario: When you have a custom DB containing client addresses for the inspection of air conditioners.
You can add a Single answer question, for example “Manufacturer” which will contain options that you can select that include “Toshiba” Mastertherm etc. and when you select the address, the manufacturer will then display as prefilled within your Custom DB.

You can also add another Text question like “Toshiba model”, but using Skip logic to display this question only for Toshiba manufacturers.
So if you pick the location with Toshiba, the “Toshiba manufacturer” questions will appear, but if you pick the location with another manufacturer, the “Toshiba manufacturer” will be hidden.

If you want to update your Custom DB from an Excel file, you can upload as many times as you need (eg update once a day if required). This is possible but please take note of the following precautions:

1. Keep the same structure of the uploaded file (same amount of columns, same identifying name of the columns in the first row)
2. You will need to have one column in the file that contains a Unique ID field (Eg system number, email address, client id etc), you will need to make sure that this is always entered within each row. You also need to set this column as a Unique Value in NestForms.

Then when you upload a new file, NestForms will merge the new data with your existing data. In this case only modified items will be synchronised into the apps.

 Please note: The text field also allows you to update your data to be exported back to your system.

Increasing and decreasing numbers

When using the Number component there is a feature allowing you to update any numerical data in your Custom DB table.

Once you have added the Number component and checked Custom DB, within the Type field dropdown you have the option to override, decrease or increase the numerical value.

When any Response is approved the number in the Custom DB will be increased (or decreased based on your selection in form builder) instead of overwritten.

This might be useful when you need to change numerical data within an inventory when the amounts of specific items have changed.

Most barcodes are numerical. So if you have an ID number in your custom DB as a column, you can add the Barcode and QR code question to your form. Tick the Custom DB checkbox and choose the related column in the Custom DB dropdown.

You should then add another Edit field and link it to Custom DB (to another column - eg Name).

Then when you scan the barcode within your app, the name will automatically prefill.

You can add multiple fields into the form based on the data you have in your Custom DB (serial number, type of device, number of devices). 

The same principle can be applied for QR codes. The only difference is that you need to decide which type of QR code you are using. For example, you can use a Link type (you need to have the exact link in the related column in your Custom DB) or you can use text (where the exact text is in the related column within your Custom DB).