© SeedCode, Inc. 2013–2023 855-733-3263
We’ve published some example code you can use to change the look and feel of DayBack for specific users. For example, this is great for removing buttons or views from certain users or user roles. More here: https://dayback.com/customizing-daybacks-look-and-feel-different-users/
Today’s update improves the way DayBack fetches new-feature notifications so it happens less often and now prevents notification fetches from happening more than they should. These notifications are the new feature announcements you’ll find when clicking on the three-dots or envelope icon in the upper-right of DayBack. (The envelope appears when you have new, unseen notifications.)
Today’s update allows the same user (email address) to be invited to more than one DayBack group in DayBack online. This is not an option for Salesforce groups, where membership is controlled by Salesforce permissions. And it’s not available if you’re signing into DayBack inside a FileMaker file: since settings from different groups are scoped to their own FileMaker files. Learn more here: Group Names
KC just added passthroughEditErrors and suppressEditEventMessages to this section of the docs, and to the notes on DayBack’s updateEvent function. Sometimes when you’re bulk-editing events, you’ll want the suppressEditEventMessages enabled to prevent the user from seeing a bunch of confirmation-toasts.
Just deployed an update that repairs an issue in Salesforce Connect where views with more than 1k events could have some events that fail to display. DayBack’s Salesforce Connect lets organizations deploy live access to their Salesforec schedules to folks who don’t have a Salesforce license. DayBack offers a few different ways to grant this kind of access. Learn more here: Calendar Sharing in Salesforce.