> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data/creating-a-booking-direct-mapping.md).

# Creating a booking direct mapping

### Introduction

This procedure describes how to create a booking direct mapping.

A direct mapping imports the exact data from your source field into Command Centre. You can create direct mappings for the following Command Centre Booking fields:

* Booking Name
* Start Date
* End Date
* Start Time
* End Time
* Interval Count
* Occurrence Pattern
* Interval Type
* Booking Reference

**Notes:**

* You can import (map) data from a single source field to more than one Booking field.
* When mapping from a database, the source field used as a direct mapping must contain a single value.
* If the Booking Reference is used, then all updates are applied to that booking and are not new bookings.

### Procedure

1. Select the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-30489e4dc6cdafeae78b7842dc608d1a686e89aa%2Fstraightbutton.gif?alt=media) tool.
2. Select the source field you wish to map from.
3. Hold down the mouse button and drag the cursor over the Command Centre field you wish to map to.
4. Release the mouse button. A black line appears between the two fields and a message appears in the window below.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-81480755f289f36ee2109a6bb4ebeecd86c8e7fe%2Fbookinginterface_directmapping.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://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-booking-data/creating-a-booking-direct-mapping.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.
