When you have several real properties cross-updating to a virtual property, you might come across the situation where two or more bookings need to be cross-updated to the virtual property for the same or overlapping dates.
When this happens the correct dates will still be blocked off, but they will be showing that there is a conflict between bookings.
In the new grid view the previously occurring phenomenon that bookings were pushed to the right and therefore were no longer showing under the correct dates has been cured.
Now the conflicting bookings are being highlighted in the grid view, but the subsequent bookings are no longer displaced.

Example:
The dates from the 10.7.2024 to the 22.07.2024 are being blocked of for the virtual property.
Though, the 18.07.2024 has been booked by two of the actual properties. This is causing a conflict of cross-updated bookings.

Property 1 received a booking for 12.07. - 19.07.2024. (brown booking)
This was cross-updated to property 2.  (green booking)
This booking is also cross-updated to property 3. (left hand part of the red & white stripped area)

Property 4 received a booking for 18.07. - 23.07.2024. (greenish-brown booking).
This booking is cross-updated to property 3 as well. (left hand part of the red & white stripped area)

This means the 18.07.2024 is being booking by both properties.

When this happens there are two possible ways to go:
1) As all days that need to be blocked out, are blocked out and the bookings are correctly aligned to the dates in the grid, there is no need to take any immediate action.
2) If you need the display in the grid view to be free of these kinds of conflicting booking scenarios, you would need to create a ticket. Please provide all the booking number, property references and dates involved and we will resolve the issue.