How to import data into Nextworld - Nextworld Documentation

Prerequisites

In order to import data from external sources, you must first gather your data and save it as a CSV file.

Data Import Definitions

In the Data Import Definitions application, you must:

Create a new record and select your destination table. This can either be an integration table, or an application table. Integration tables require additional configuration steps. Learn more in Data import integration configuration.
In the File Type, select CSV File.
On the Mappings page, in the Data Mappings subtable, map your external data into the destination table's fields. Learn more in Data import mapping configuration.
On the Processing page, you can configure your error tolerance and dictate what logic blocks you want run at the time of data import.
On the Import File Details page, select Attachment for your File Location Type.
Once the record is saved, select the Attachments form action to attach your CSV file. Delete older attachments from the definition to avoid importing redundant data.
Select the Run Import row action to import the data.

How the definition was configured determines where the imported data is sent. Data can be imported into an integration table, or directly into the destination table. If data is imported into an integration table, there are additional steps in the import process.

Integration table import

If the data is imported into an integration table, you must:

Navigate to the integration application built over the integration table.
Select the Process Run form action. This processes and modifies the data before it is sent to the appropriate internal application table.
External data is imported into the integration table selected in the data import definition's Destination Field.

How to use Quick Import

Use the Quick Import feature to directly import external data into an application record. Quick import is only available in Header Detail applications which were configured with this feature during development.

Access Quick Import inside of the application record where you want the external data. Open the form action menu and select Import Data to open the Quick Import window and download the CSV template.

Fill out the CSV template then open the Quick Import window and either:

Browse and select your saved CSV template, and then select Import.
Copy the data from the template directly to your clipboard, and select Import From Clipboard.

The data from your file is brought in as detail lines that you can edit in the application.

CSV template considerations

Column names in your CSV template use the internal name, also called a data item name, of the fields in the application. To view the internal name of a field, open the help text for that field and hover over the first value on the bottom of the window.

Search fields, also called table lookup fields, reference information that is maintained in other applications. A search field can point at a single field, or multiple fields, within the other application. If the search field references multiple fields, you may see multiple columns for the same data item name. For example, Organizational Unit may reference both the Name and Numeric Code fields. This would allow you to have unique values for org units with the same name, but different numeric codes.

Column headers in the CSV template have the following formats:

Field Type	Template Column Header Format	Example	Explanation
Traditional field	[Field Name]Data Item Name	[Units] UnitAmount	Units is the name of the field you see in the application. `UnitAmount` is the internal data item name you can see by opening the field level help.
Required fields—Indicates you must enter a value or the import fails.	[Required][Field Name]Data Item Name	[Required] [Line] GLLineNumber	Line is the name of the field you see in the application. `GLLineNumber` is the internal data item name you can see by opening the field level help. Required indicates it is a required field in the application record.
Search fields—Also called Table lookup fields.	[Field Name]Data Item Name_Related Field	[GL Account] GLAccount_AccountNumber [Account Name] GLAccount_AccountName	GL Account is the name of the field you see in the application. `GLAccount` is the internal data item name you can see by opening the field level help. `AccountNumber` and `AccountName` are the related fields used together to find the correct GL Account record.
Composite fields—Fields made up of multiple components, such as address or currency fields.	[Field Name]Data Item Name_Composite Component	[Debit Amount] TransactionDebitAmount_CurrencyCode [Debit Amount] TransactionDebitAmount_CurrencyBigDecimalValue [Debit Amount] TransactionDebitAmount_CurrencyDecimals	Debit Amount is the name of the field you see in the application. `TransactionDebitAmount` is the internal data item name you can see by opening the field level help. `CurrencyCode`, `CurrencyBigDecimalValue`,and `CurrencyDecimals`are the components of a composite field that together create a single field value. For example, to fill out these columns for a transaction amount of $10.52 USD, you would put the following values in each column: CurrencyCode: USD CurrencyBigDecimalValue: 1052 CurrencyDecimals: 2

Example CSV Format

Example of filling out the CSV Template:

[Required] [Line] GLLineNumber	[GL Account] GLAccount_ AccountNumber	[Account Name] GLAccount_ AccountName	[Debit Amount] TransactionDebitAmount_ CurrencyCode	[Debit Amount] TransactionDebitAmount_ CurrencyBigDecimalValue	[Debit Amount] TransactionDebitAmount_ CurrencyDecimals	[Units] UnitAmount
1	13100	Raw Inventory	USD	12100	2

Some CSV templates have columns that do not match any visible fields on the application. These columns can be optional or mandatory, depending on the application.