Dimensions are a powerful way of letting Booker25 know about records on any standard or custom object that are related to Reservations in, either through a lookup or via a junctionobject:
Through a lookup
The Reservation object has a lookup to the other object.
An example of this is the Resource object, to which Reservation has a lookup.
Via a junction object
The Reservation object is linked to the other object through a third object, which has lookups to both Reservation and the other object. This Salesforce knowledge article explains what a junction object is.
An example of this the Contact object, which is linked to Reservation through the ReservationContact junction object. ReservationContact has a lookup to Reservation and to Contact.
By using Dimensions, Booker25 knows that these related records should be included in Booker 25 logic. This allows you to:
Include those related records in the Booker25 conflict checking logic
define the lookups as being intelligent, and that way only retrieving available options when adding them to a reservation (only work with lookups)
create calendars for those records, that will show reservation. This means you could show a single calendar on a contact record page on which you show tat contact’s reservations.
Out of the box Dimensions
The following Dimensions are included with Booker25 after install:
Resource
Staff
Group
Contact
You can modify these Dimensions or even delete them if you are sure you don't need them.
Performance
For performance reasons, it's good practice to only have the minimum number of Dimensions, especially ones that are configured for conflict checking.
Video
For a more visual introduction to Dimensions and an example of how they work, please have a look at this video.
The remainder of this article and the sections below will explain in more detail how to set up Dimensions, Dimension Fields and Dimension Junctions.