> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v6/dataflows/maps/creating-direct-maps.md).

# Creating Direct Maps

Direct map is used when data from an object should flow to another object without any changes to the data. The data is transferred ‘as is’ from a designated field in the upstream object to a designated field in the downstream object.

{% hint style="info" %}
**Note:** The data may still get converted to fit the destination field’s data type.
{% endhint %}

Direct maps are displayed as solid lines on the dataflow.

An example of what a *Direct Map* might look like is shown below:

![](https://3768133094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH4WCHHphSt0ALtMJlqot%2Fuploads%2FK4a97TwZNllEc1rpMjNf%2F0.jpeg?alt=media)

To create a direct map between the fields of two objects, drag the field’s input port of the downstream object and drop it on the field’s output port of the upstream object.

## Direct Map Types

There are four direct map types:

1. *Value Map:* This is the default map type. It is always created when a new map is created between two fields. A Value map transfers the field’s value between the two mapped fields.
2. *Field Name:* This map type will write the source’s field’s name to the destination field. Note that the destination field should have a suitable data type, such as String.
3. *Field Header*: This map type will write the source’s field’s header to the destination field. Note that the destination field should have a suitable data type, such as String.
4. *Field Data Type:* This map type will write the source’s field’s data type to the destination field. Note that the destination field should have a suitable data type, such as String.

To change a map type, right-click on the map line and select *Change Map Type* from the dropdown.

## **Usage**

The objects in this dataflow example are connected via direct field maps. Direct maps make it possible to connect the source field to the mapped destination field.

![](https://3768133094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH4WCHHphSt0ALtMJlqot%2Fuploads%2Fsixq9cBmQGgWTF5icxpa%2F1.png?alt=media)


---

# 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://documentation.astera.com/astera-data-stack-v6/dataflows/maps/creating-direct-maps.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.