Viewing Linked Reservations

Top Previous Next

When showing a list of linked reservations in Reservation Details or the Quick-info window, a tree-structure list is used to indicate the portfolio levels and also the type of linkage for each reservation. These symbols are used to indicate the link relationship with the owner reservation (the portfolio type):

= Synchronized

# Non-synchronized

> Sub-member

Note that in the tree structure, the top-level reservation won't have an indicator, because it's not a member of any higher portfolio. This top-level reservation is considered the "Master" of the linked reservations.

In some cases, an asterisk ( * ) will be shown in front of one of the reservations. This simply indicates which one you're currently viewing.

Here is an example diagram of a fairly complex set of linked reservations, as it would appear in the drop-down list on Reservation Details or on the Quick-info window:

RV 1 [Linked master]

= RV 2 [synchronized with RV 1]

> Stall 1 [sub-member of RV 2]

= RV 3 [synchronized with RV 1]

# RV 4 [not synchronized]

> Boat slip 1 [sub-member of RV 4]

> Kayak 1 [sub-member of RV 4]

# RV 5 [not synchronized]

This looks confusing at first, but it will make sense once you learn the symbols and notice the spacing to indicate levels/ownership. Also note that the relationships are clearly detailed in case it's not obvious from the structure. There's a step-by-step example of creating these reservations in the "Creating Linked Reservations" section.

In portfolio terms, there are 4 portfolios involved:

• RV 1 owns 2 portfolios -- a Synchronized portfolio containing RV 2 and RV 3, and a non-synchronized portfolio containing RV 4 ad RV 5.

• RV 2 owns 1 portfolio -- a Sub-member portfolio containing Stall 1

• RV 4 owns 1 portfolio -- a Sub-member portfolio containing Boat slip 1 and Kayak 1

However, you can pretty much forget about "portfolios" now. While that's the way it's stored and managed internally, the only thing you're concerned with is their "link relationships", which are already detailed in the tree-structured list.

A couple important notes about this example:

•Since all synchronized and sub-member reservations are combined for billing (and any synchronized or sub-members of those, etc. all combined with their top-level owner), the reservation for RV 1 will also contain all transactions for RV 2, RV 3, and Stall 1. However, non-synchronized reservations are considered separate "sets" or "top-level reservations" for billing -- so the reservation for RV 4 will include transactions for Boat slip 1 and Kayak 1, and RV 5 will only contain transactions for itself. Thus by using appropriate link types, you can completely control which reservations are combined for billing.

•Only synchronized reservations will maintain identical dates and status. Thus RV 1, 2, and 3 will stay synchronized if a change is made (assuming the appropriate answers are given when prompted to keep them synchronized). But changes to any of the others will only affect that reservation.