> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/dynamic-components/tutorials/components/calendar/show-booking-details-on-hover.md).

# Show Booking Details on Hover

Add the training room to an Avonni Calendar event popover so coordinators can confirm the location and time without opening a Salesforce record.

The timeline shows when training is booked. Give the coordinator a way to check the room from the same view by adding the Salesforce Event location to Avonni Calendar's event popover.

<figure><img src="https://2532358799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FODPvvv7Cx9Z9RECLn3oV%2Fuploads%2FDV7bMqXdmFglL2ewj8iY%2Fcalendar-show-booking-details-on-hover-result.png?alt=media" alt="Safety Drill popover with the Maple Room location and the booking times." width="640"><figcaption><p>The Room field shows the location stored on the Salesforce Event.</p></figcaption></figure>

## Before you start

* Complete [Build a Resource Timeline from Salesforce Records](https://docs.avonnicomponents.com/dynamic-components/tutorials/components/calendar/build-a-resource-timeline.md). Use the sample Events with different values in `Location`.
* Confirm the test user can read the Salesforce Event location.

## Steps

{% stepper %}
{% step %}

### Add the room to the event popover

Select the Calendar in Component Builder. In **Properties**, open **Event Display > Popover Fields**.

Keep the existing start and end fields. Add a field, select Event `Location` in **Value**, and enter `Room` in **Label**.

<figure><img src="https://2532358799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FODPvvv7Cx9Z9RECLn3oV%2Fuploads%2FC62vYx6vcLuclK0ecVRv%2Fcalendar-show-booking-details-on-hover-fields.png?alt=media" alt="Popover Fields showing from, to and Location labeled Room." width="640"><figcaption><p>Keep the time fields and add Location with the label Room.</p></figcaption></figure>
{% endstep %}

{% step %}

### Save and test

Save the component and open the sample booking day on the test page. Hover over Safety Briefing or focus the event with the keyboard. The popover should show Cedar Room along with the booking time.

Hover over Safety Drill and confirm the room changes to Maple Room. Compare both values with the corresponding Salesforce Event records.
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>The popover shows the times without the room</summary>

Check that the Event has a value in `Location` and that the viewing user can read it. In **Popover Fields**, check the selected **Value**. The **Label** only changes the text displayed next to the value.

</details>

## Related tutorials

* [Filter and Search Bookings](https://docs.avonnicomponents.com/dynamic-components/tutorials/components/calendar/filter-and-search-bookings.md) to find the right booking before inspecting it.
* [Calendar reference](https://docs.avonnicomponents.com/dynamic-components/components/calendar.md) for the **Event Detail Popover** slot if you need to place other components in the popover.


---

# 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://docs.avonnicomponents.com/dynamic-components/tutorials/components/calendar/show-booking-details-on-hover.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.
