Upgrading from an older version

Owned by Luuk Koetsier (Unlicensed)
Last updated: Jul 12, 2023
5 min read

 

If you are upgrading from an older version, it might be needed to take some admin actions.

4.29 

  • Add the Reservation Type Status related list to your Reservation Type page layout(s).

  • Optionally, also add the Reservation Type Status related list to your Reservation Status page layout(s).

  • Add the 'Weekend Highlight Color' field to your View page layout(s)

4.32

  • Add the ‘Start Time’ and ‘End Time’ fields to your View page layout(s).

    • Assign the ‘Allow Reservation Deletion When Updating Recurring Reservations’ permission to users that need it.

4.39

  • Add the Default Quantity field to your Service page layouts.

    • (Optional) To preserve existing behavior, the upgrade will set the Default Quantity of all your existing Services to 1. Adjust this number for each Service if desired.

4.40

  • Add the Column Hiding Behavior picklist to your View page layout(s).

    • Remove the ‘Hide Closed Times Without Reservations’ and ‘Hide Times Without Reservations’ checkboxes from your View page layout(s).

    • Review the article on Column Hiding Behavior to see what options are available.

    • Add the Default field to your Resource Layout page layout(s).

4.47

  • Add the new checkbox ‘Disable Progressive Rendering’ to your View page layout(s).

    • We are deprecating the GoMeddo Read Only permission set. This means that you can still use it, but we will not be updating it with new fields. Make sure your security model does not depend on this permission set being kept up to date.

    • Check if you have translations for, or are referencing any of the following custom labels: CapacityExceeded, Capacity Exceeded Combined With Other Reservations, ReservationConflicts, Reservation Conflicts Without Times. These labels now have an additional merge parameter and you should review their usage.

    • Delete the now obsolete checkbox fields ‘Hide times without reservations’ and ‘Hide closed times without reservations’ from the View object, unless your own solutions depend on these fields.

4.50

  • Add the new ‘Dimension Name Field’ to your Dimension Junction Display Setting page layouts.

    • The ReservationContact object is now related to Contact through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.

    • The ReservationContact object is now related to Reservation through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.

4.51

  • Confirm that your ordering of hover fields is correct after upgrading, because these have been reversed for the Lightning calendar as part of a bug fix.

 

4.56

4.57

  • 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.

4.60

  • Add the new ‘Dimension Name Field’ to your Dimension Junction Display Setting page layouts.

    • The ReservationContact object is now related to Contact through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.

    • The ReservationContact object is now related to Reservation through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.

4.61

  • This version will automatically update any View records with a Slot Duration of ‘30’ (which indicates 30 seconds) to ‘00:30’ (which indicates 30 minutes).

    • When upgrading, you might get the following error: Lightning_Calendar: In Lightning component B25:multiCalendarWrapper, property calendarId has an invalid value Resources. This happens if you have previously deleted the default calendar named ‘Resources’. To get around this error, simply create a new calendar named ‘Resources’ and try again.

4.63

  • If you are upgrading, do the following to get the most out of this release.Add the new related list named ‘Related Lists’ to the Reservation Type page layout.

 

4.66

  • Add the new Hide Service Section field to the reservation type layout

    • Add the Prevent Horizontal Drag and Prevent Vertical Drag to the Multi Resource Calendar Layout.

    • Add the Display as Link field to the Hover Field layout

    • Add the Display as Link field to the Related List Field Layout.

4.74

  • There is a new field on the reservation type “hide recurring section” please give your users access to this field and add it to the page layout.

    • There is a new field on Dimension that specifies the “Dimension Name Field”. Please give your users access to this field and add it to the page layout. The field should fallback to “name” as a value.

4.76

  • There is a new field on Availability “Is Dependent Availability” please give your users access to this field and add it to the page layout. The Multi-calendar for record pages now has the option to say it should take these availabilities into account, there is a new checkbox in the lightning page builder called "Availability Filter" to activate this feature.

4.78

  • Drag the Hover Definition component to the Record page for Hover definition object in the lightning page builder

    • Drag the Title Definition component to the Record page for Reservation Title Group object in the lightning page builder

4.81

  • If you want to use the occupancy component, you need to add it to the dimension record pages.

    • If you run into an installation failed error it might be necessary to change the “IS Installing” custom setting to true:

      • - Go to Setup

      • - Search for Custom Settings

      • - Click Manage next to System Setting

      • - Change the value to true.

    • If you don’t have that setting, follow the following steps:

      • - Go to SetupSearch for Custom Settings

      • - Click Manage next to System Setting

      • - Click NewName the record IS_INSTALLING, and for Boolean Value true

4.82

  • If you want the QR code to check-in make sure to add it to the reservation contact page layout.

4.84

  • It should be enabled already for all organizations, but it's necessary that Folders and Enhanced Sharing is enabled.
    So if you face any installation errors, please take a look there

4.85

  • Add the field Allow Unavailable Bookings to the Reservation Status page layout.

    • Add the field Reservation Skip Availability Field to the Dimension page layout.

4.86

  • The changes made to the double booking matching conditions are not backwards compatible. If you currently use a double booking matching condition you will have to convert that condition into a Custom Metadata Type and change the reference on the dimension record. See our documentation on this.