Besides a number of bugfixes, this version introduces record pages with calendars and makes calendar components deployable. This comes with an important caveat if you are already using calendar components, so make sure to check the Admin Actions below.

‍

Features

• Lightning calendar components now reference calendars by name instead of id. This has the major advantage that pages containing calendar components are now deployable between orgs.
• Lightning record pages for Resource and Staff have now been included. These are identical to the default record Lightning calendar components, except that they include a Calendar tab with a Lightning calendar component.
• It is now possible to create calendars without dimensions. This also means you can now easily add calendar components to objects without first having to create a dimension for them.

‍

Bug fixes

• The ordering of time headers on the Lightning multi calendar was incorrect. The ordering was exactly opposite of the VisualForce calendar. Also an order of ‘0’ (zero) was treated as if the value was ‘null’ (empty).
• The 'Capacity' record type on Conflict has now been included in all permission sets.
• The Reservation Status tab is now accessible through the B25 Admin permission set.
• Currency and checkbox fields of records in a junction list were sometimes emptied when rerendering the VisualForce reservation form.
• Ordering of junction lists on the Lightning calendar was incorrect.
• The reservation form on the Lightning calendar did not validate a field as required if it was marked as required in the field set.
• The ‘N/A’ option for filter fields on the Lightning calendar is now also supported by picklists.
• Cells shorter than 1 hour caused incorrect hiding of cells.
• The ‘View in Salesforce’ button in the Details section of the Resources & Types tab did not work properly.
• Automated Booking Rule logic is no longer executed from the Opportunity trigger when the user has no access to the Automated Booking Rule object, or no Automated Booking Rules are configured in your org.

‍

Admin Actions

If you are upgrading, do the following to get the most out of this release.

• Important! Because calendar components now reference calendars by name instead of id, if you have included any components on your own pages, they will give an error message that the calendar can’t be found. To fix this, simply edit the page and re-select the correct calendar.
• If you have wrapped any calendar components inside your own components, you will need to change the value passed into the calendar-id. This value should now be the calendar name instead of the id.
• Check if your time headers on the Lightning calendar are ordered correctly. Configuring time headers is described here.
• On install or upgrade, two dimensionless calendar config records will be created automatically. These have been included for convenience, so you can easily add calendar components on objects for which no dimension exists. Feel free to delete or modify these calendar records.

‍