> For the complete documentation index, see [llms.txt](https://manual.senseforce.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.senseforce.io/manual/sf-platform/event-schema-management/importing-a-event-schema.md).

# Importing a Event Schema

If you do not want to set up your event schemas manually you can also use the "Import Schema" function.

![Enter the Event Schema Management, then click "Import Schema".](/files/-MDEXNsgDU9XcqqXQ_p2)

To create a schema via import you just need to create a text file and save it with the file extension **.csv**. Within the text file, you need to apply some rules, such that your definition is interpreted correctly. An example for a valid .csv would be,

```
Key;Name;Datatype;Units;Decimals
BW_0;Wind Speed;long;km/h;
BW_1;Day of Week;string;-;
```

The first line needs to be the same in every definition. In this example the following lines define attributes with keys BW\_0/BW\_1, names "Wind Speed"/"Day of Week", data types long/string, units km/h/- and no decimals.

### Does and Don'ts

* The keys are not allowed to contain whitespace characters.
* The units need to contain a non-whitespace character (if you do not want to assign a unit use "-").
* Allowed keywords for the data types are string, boolean, long, double, timestamp, and integer. The datatype definition is case insensitive. So the can be written in upper or lower case. 
* If you use the data type double you need to assign a number of decimals (for every other data type this is ignored).
* The keys are not allowed to be equal to "id", "inserted", "size", "thing", "timestamp" or "type". Because they are always added automatically to each schema and therefore these keys are already used.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manual.senseforce.io/manual/sf-platform/event-schema-management/importing-a-event-schema.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.