Field & Object Mapping in Salesforce

Tell DayBack About Your Salesforce Objects

This article guides you through the process of creating a new calendar in DayBack and linking it to your Salesforce objects by mapping each necessary field. You can create calendars for both standard and custom Salesforce objects. A helpful video is included below to walk you through the process.

To configure DayBack with your Salesforce objects, you need to complete a form on DayBack's source settings screen. Each mapped object will appear as a separate calendar source in DayBack, and you can choose which sources to display at any given time. DayBack provides a few standard objects by default, including Events, Tasks, and Campaigns, which serve as mapping examples for creating calendar sources for your custom objects.

If you're using Salesforce Scheduler, the default object will be Service Appointments. You can extend and customize this by adding new objects to show resources' availability or vacation requests.

The Field Mapping form will list the fields available in DayBack and highlight any required fields you may need to add to your custom objects. You can disable any fields you don't need or are unsure about. Fields without an "enabled" checkbox are required for the calendar to function - an event's start time, for example:

As an org admin, you are already an administrator in DayBack. Clicking on "Settings" in the calendar's left-hand sidebar will reveal an "Administrator Settings" button, allowing you to configure your calendar sources.

Getting Started with Field Mapping

Here's a step-by-step walkthrough of creating a new calendar and adding your field mapping:

Having first created your new source you'll continue editing the calendar settings by mapping the fields DayBack needs to know about in order to show your object on the calendar.

Required fields

DayBack requires only a few fields in your object, which are usually already present, especially for standard objects. For custom objects, ensure you have the following fields:

1. Start:
   • The starting date or date/time of the object. If your object only has one date field, like a due date, use that field here.
   • Refer to the next section for details on changing date and time display.
2. Display:
   • This field (or fields) appears when you view the event in the calendar. It represents the name of your event, such as "Meeting with Tim".
3. Title:
   • This may be the same as the first field you choose in Display. It is the editable title shown in the popover when you edit an item in the calendar.

Date & Times in the Display Field

DayBack has a default format for displaying event start times, which can vary depending on the view. However, you might prefer a consistent date and time display across all views. To achieve this, configure the display field setup for events when setting up your Salesforce objects in DayBack. This allows you to control how event times are shown for each object.

1. Adding Date/Time Fields:
   • Any date or dateTime field can be added to the display field. Dates and dateTimes will be rendered in the local format. DateTimes will appear as times (e.g., 4:00pm) and dates will show in the local date format (e.g., 12/11/2023).
2. Hiding Default Start Time:
   • You may want to hide the default start time to display your own time format. Field can be hidden using CSS within DayBack's CSS settings. Use the following CSS to hide the default time:

.fc-event-time.time {
  display: none;
}

3. Configuring the Display Field:
   • Add the start and end times into the display field with custom formatting. For example:

<dbk-css style="font-weight:bold">StartDateTime</dbk-css> - <dbk-css style="font-weight:bold">EndDateTime</dbk-css>,
Subject,
Who.Name

By customizing the display field, you can create a consistent and informative view of your events across all calendar views.

Special Fields: Status and Resource

The status and resource fields in DayBack have unique roles. The status field is used for color-coding your items, while the resource field assigns items to columns in the resource scheduling views.

DayBack color-codes your events based on the value in the status field. This is typically a temporal attribute of the event, such as whether it has started or if a patient has checked in. However, it can also be used to distinguish different types of work, departments, or payment statuses (e.g., green for paid, orange for pending, grey for canceled).

• Mapping Status: You can map the status to any field in your object, including a picklist. Then, adjust the list of possible statuses in DayBack's filters tab to match the values you want to see.
• Video Guide: Here's a step-by-step guide on mapping the status field in Salesforce.
• Color Coding Guide: For more information on color-coding your items, see Event Colors & Status.

Resource scheduling is a key feature of DayBack, and we encourage you to read detailed information in the Resources Overview. To get started:

• Default Mapping: DayBack defaults to mapping the resource to "Owner.Name " for Events and Tasks objects. This assigns the item to the logged-in user if the resource field in DayBack is left blank.
• Custom Mapping: You can also map the resource field to any text field or multi-value picklist.

For more details on mapping the resource field, refer to Mapping the Resource Field.

Using Custom Fields

You can include custom fields in your calendar mapping. Note that Salesforce appends a suffix to custom fields. For example, if you have a custom field named "Sample," the field's name in Salesforce will be "Sample__c " (without the quotes).

Adding more fields to an Event's Popover

You can enhance DayBack's event popover by adding additional fields, which is especially useful for including required fields when creating new items.

These are fields that DayBack does not have currently have space for in the mean popover, but which will appear in a scrollable drawer beside your event popover. These fields are searchable using DayBack's text filter, allowing you to refine your calendar views with text filters that can be saved as bookmarks.

Learn more about custom fields here: additional fields.

Enhancing or Replacing the Event Popover

Learn more about customizing, or replacing the DayBack's native Event Popover with your own.