Many improvements, mostly to the new Lightning calendars.

‍

Features

• GoMeddo now includes a Multi Calendar Lightning component which can be placed on Lightning record pages, to display the children of that record. For the how-to article, see here For an overview of available calendars, see here.
• There is a new checkbox property ‘Show Availabilities’ on the Multi Schedule component. When enabled, any relevant availabilities with the checkbox ‘Include On Scheduler’ set to true will be loaded and shown to the user. When disabled, every row shows as always open. This property is enabled by default. For more information: see here.
• The Lightning calendar now remembers the user’s last selected view when the page is reloaded.
• The Lightning calendar now respects the ‘Prompt before moving’ and ‘Prompt before resizing’ checkboxes that have been configured on the calendar configuration record.
• Links on the Lightning calendar now open a new Salesforce tab or a new browser tab instead of navigating away from the calendar.
• The Lightning calendar’s reservation form now also has a view mode, as opposed to only an edit mode.
• The Lightning calendar’s reservation form now hides the Pricing section if the global setting ‘Resources have a price’ has been disabled.
• The resource lookup on the Lightning calendar’s reservation form now also searches in the resource’s context (parent and grandparent names, as shown between parentheses in the results).
• Controlling and dependent lookups and picklists are now supported on the Lightning calendar’s reservation form.
• Admins can now configure the height of Lightning calendar components using the new ‘Max height’ property.
• The picklist property ‘Calendar’ on the Single Calendar component will now only show valid calendar records. Valid records are Calendars of the ‘Single’ record type, linked to a Dimension that is of the same object type as the record page that you want to add the component to.

‍

Bug fixes

• Reservation titles on the Lightning calendar would break if they were cross object references (like B25__Resource__r.Name).
• The alignment of reservation titles on the Lightning calendar was incorrect for reservations that started before the current view started.
• The Lightning calendar no longer breaks when Dynamic Dimension Groupings include a ‘None’ option. For more information on Dynamic Dimension Groupings, take a look here.
• Dynamic Dimension Groupings on the Lightning calendar now show the record name instead of the id, if the grouping field is a lookup.
• Dimension junctions that the user does not have read access to are now hidden on the Lightning calendar’s reservation form, instead of throwing an error.
• If the user does not have create access on the Reservation object, the reservation form on the Lightning calendar now simply does not open, instead of throwing an error.
• The search results for lookups on the Lightning calendar’s reservation form are now consistent with the VisualForce calendar.

‍