> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/data-and-data-tables/create-data-table-from-external-file.md).

# Create Data Table from External File

Data plays an important part in your applications and LogicNets allows you to import tables using your existing data in the Comma-Separated Values (.csv) or Tab-Delimited (.txt) format. You can quickly upload and import your data to the resources/data subfolder of your project and access and use the data values as part of your project's modeled processes.

## Prepare External File for Import

Before loading the information into LogicNets you need to perform a few checks to create the file for import:

* Review the column names. The system will use these to create table column names when loading your data.
  * Ensure each column has a unique name in the first row of the data source.
  * Convert column names to all lowercase text.
  * Replace spaces in column names with the underscore character; for example, *Product Code* should be *product\_code.*
* Review your data for errors, missing information, or carriage returns and other special characters that may interfere with the upload.
  * Depending on the source program, some characters may be hidden from view and may cause the import process to fail. If your file fails or does not contain all of the data you expected, you can repeat the upload after correcting the errors.
* Save your source document in either the .csv or tab-delimited .txt format. Both options are available in the *Save As* menu in Microsoft Excel and other spreadsheet programs.
  * If your information is text-based and resides in tables in Microsoft Word or similar programs, copy and paste the data into a spreadsheet program first.

## Load and Verify Data

Take the following steps to load the data into the LogicNets Designer.

1. Open your project and navigate to the resources/data folder.
2. Select the *Import Table* icon.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6bd1e75d631bca2eba7996ce6cedb383742b6344%2Fcdc1adad-1b01-45e6-8d3b-af2b4e03d4a1.jpg?alt=media)
3. Enter your table name in the Table name field. Type in your desired table name lowercase and uppercase letters, numbers, and underscores are allowed in the name field. Spaces are not allowed.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f45d9526227bdfcf78682f1db5b2fd69c903116c%2Fc74a33f5-b2f9-4718-a5ed-3b70fb20b19d.jpg?alt=media)
4. Click *Choose File,* locate the csv/txt file on your local drive, and click *Open.*
5. Click on *Upload* to upload your file.
6. If there are no errors, the system loads the data and opens the table.
7. Verify the data was loaded successfully. If there are errors you can do one of the following:
   * delete the table, correct them in the source file, and repeat the steps above,
   * use the buttons above the data list to make the edits directly in the table in the Designer.![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-8bece753cab2a026c691f3d868e17b037c82fd75%2F76f2b0cb-0872-4ba1-a93b-5fb28bf0540b.jpg?alt=media)
8. Verify that the system has correctly assigned the data type to each column by clicking on the *modify* button. The system displays a view of the table structure and you can correct any column definition errors here, including column name and type. You can also add captions to the column and add or remove columns. To do this from this screen use the *Mode* dropdown menu to select *Add/Delete Columns.*

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-95765316e79c403f5c8ff65ccf587a158ac9b924%2F446aab3f-1722-49e9-a986-ed57105e544c.jpg?alt=media)

## Tips and Tricks

Watch out when using Microsoft Excel to create a TAB separated .txt file from a spreadsheet. If the first few records don’t have values for all fields, Microsoft’s engine will strangely add a SPACE on either side of the column name. (This has been reported by CL users on the internet and may be a defect or undocumented functionality). This typically goes unnoticed unless you use a Text Editor that highlights the various hidden characters. When the LogicNets table engine receives this file, the spaces are replaced with an underscore prefix and suffix to the column name, so “col1\_name” is created as “\_col1\_name\_” in the data model.

### Special Characters in Source Data

If your data includes any special characters such as "±" or "≥" in text strings, you should use the CSV UTF-8 format instead of the normal CSV.

In the event the import does not correctly interpret all characters, try editing each cell manually (or if there are a large number of edits, contact LogicNets for advice).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/data-and-data-tables/create-data-table-from-external-file.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.