Importing data to Ninox

To import a CSV file to an existing or a new table in Ninox:

1. Go to the database where you want to upload your CSV file.

2. Click on Import Data.

3. The Import Wizard opens and you click the Import CSV file button in the Import data pop-up.

4. Select the appropriate file on your device and click Open, follow the prompts until you see your data, and click the Import now button in the bottom right corner to import your data. Done!

That was the quick tour! On the way, you have certainly seen that you can do much more there.

Using the import wizard

Using the Import Wizard (we named the pop-up this way for simplicity), you can set various options.

Data source settings

Help the Import Wizard by giving it details about the data you want to import.

Import settings

Specify which data should be imported and what exactly should happen to it.

Click Next and the following pop-up appears:

Naming the table

In the next step, name the table and assign fields.

Think of a modularized database like a set of toy blocks. Each block, or module, is a separate piece of the solution and has its own job. Just like you can snap together blocks to make different things, you can connect these modules to build a complete solution or application.

Every module is like its own database. It works by itself and has its own information and tasks it can do. But, when you put these modules together with others, they can share information and do more complex jobs.

Let's take a company as an example. It has departments like sales, human resources (HR), and accounting. In a modularized database, each department has its own module. The sales module keeps track of talking to customers, the HR module looks after employee details, and the accounting module deals with money matters. Each of these parts works on its own, but they can also connect to each other. For example, the HR module could share employee information with the sales module to help track who's selling well.

Think of a modularized database like a set of toy blocks. Each block, or module, is a separate piece of the solution and has its own job. Just like you can snap together blocks to make different things, you can connect these modules to build a complete solution or application.

Every module is like its own database. It works by itself and has its own information and tasks it can do. But, when you put these modules together with others, they can share information and do more complex jobs.

Let's take a company as an example. It has departments like sales, human resources (HR), and accounting. In a modularized database, each department has its own module. The sales module keeps track of talking to customers, the HR module looks after employee details, and the accounting module deals with money matters. Each of these parts works on its own, but they can also connect to each other. For example, the HR module could share employee information with the sales module to help track who's selling well.

Availability

Capacity

The pricing page (section on Essentials) offers info on how many renders per month are available in your subscription.

How print customization works in Ninox

Ninox uses a third-party integration, carbone.io, to find all markers {} in a document (.xlsx, .odt, .docx, ...) and replace these markers with Ninox data.

According to the syntax of your markers, the following operations can be performed:

• replacing a field

• formatting data

• repeating a document portion (a table row or anything else)

• looping on unlimited nested arrays

• conditionally displaying a data based on a test expression

The syntax is similar to using a JSON Array or Object in JavaScript. Combined with features of, for example, Microsoft Word or LibreOffice, you can create documents with:

• graphics

• headers, footers

• automatically repeated table header across pages

• insert computed field

• page count

etc.

Supported file formats

Import

• .xhtml

• .odt

• .ods

• .odp

• .docx

• .xlsx

• .pptx

• .odg

Export/print

• .pdf

Supported fonts

Google Fonts are pre-installed. If a font is not rendering into documents, verify that font is available on Google Fonts.

Supported functions

Functions for standard printing

• printRecord(nid, layoutName)

  • prints default report

• printAndSaveRecord(nid, layoutName)

  • prints default report and returns the link

Functions for dynamic printing

• printRecord(nid, templateLayoutName, data)

  • prints dynamic report with your custom layout

• printAndSaveRecord(nid, templateLayoutName, data)

  • prints dynamic report with your custom layout and returns the link

Key features at a glance

• Simplified database navigation, boosting data access speed and productivity.

• Avoids complex API workarounds.

• Seamless integration with existing database relationships.

• Consistent read and write client-side operations across both web and native apps.

• Intuitive functionality in line with other Ninox transactions; do as transaction ... end, do as server ... end, and