> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/appointment.md).

# Appointment

Use an **Appointment** field when the record should store a time range with a start and end.

For the general settings all data fields have in common, see [Shared field settings](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/shared-field-settings.md).

Field-specific settings for **Appointment** are:

<i class="fa-airplay">:airplay:</i> **Display**

* **Show in calendar**: controls whether the appointment appears in calendar-based views
* **Color**: sets the color used for the appointment
* **Display as**: defines how the appointment is shown

Click the **Display as** field to open the [Logic editor](/ninox-scripting/automate-your-workflows/explore-core-scripting-elements/logic-editor-features.md). There, you define what appears in the calendar view. Keep in mind that space in the calendar view is limited.

On the form, the field shows a start date and time plus an end date and time. You can enter the values directly or click the <i class="fa-calendar-days">:calendar-days:</i> calendar icon to open the picker.\
If the format is set to a 12-hour option, you can switch between **AM** and **PM** by typing **A** or **P** in the field. You can also press the up and down arrow keys to switch between **AM** and **PM**.

{% hint style="info" %}
Use **Appointment** for meetings, bookings, or events with a start and end. Use **Date and time** when you only need one date and time value.
{% endhint %}


---

# 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://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/appointment.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.