Mapping the Resource Field in Salesforce
Resource scheduling is one of the real strengths of DayBack calendar, and I'd encourage you to check out some of the resource scheduling views here: Resource Scheduling.
As part of setting up your calendar, you'll tell DayBack which field holds the data for your resources. This article The rest of this article describes which kinds of fields you can use for resources.
In this article
What is a resource?
A "resource" is anything in your org that can get overscheduled: a room, a person, a team, or even a business process. The resource views give you a dedicated row or column for each resource so that you can easily see which are overscheduled, which have gaps, and drag events from one resource to another.
In field mapping, you'd select the field in your event or appointment object containing your resource. For example, in the native Event object, the resource is usually a person, and the field is usually Owner.Name. In a custom object, you may have created a field for the truck or technician that's your resource.
The rest of this article describes which kinds of fields you can use for resources on the "Resources" tab of field mapping. Each kind of field has its own advantages and disadvantages.
Note: In addition to field mapping, you'll also add resources to DayBack's left-hand sidebar so that you can filter the calendar by resource and group your resources into folders by skill or location. You'll find information on how to do that here: Adding, Removing, and Sorting Resources.
Owner.Name - the default for Events, Tasks, and Campaigns
By default, DayBack maps resources to the Owner.Name field in your Event and Task objects. This works great for many applications.
There are some downsides to using owner (maybe these are downsides to using Events, and some Salesforce developers will decide to use a custom object instead). Salesforce doesn't permit multiple values for owner, you can't have multiple values here, and you can't leave the owner blank (or drag an event to the "none" column in DayBack).
Since you can't have multiple values in an owner, you can create multiple instances of the same event instead: control-drag or option-drag an event to a new resource to quickly create a copy of the event.
To use Owner.Name, leave the switch for "My Resource is a Related Field" set to "no" and select "Owner.Name" from the drop down list of available fields.
Note: DayBack will clear out your resource selection whenever you toggle the switch for "My Resource is a Related Field" so please double-check that you have selected a field there.
Text fields and multi-selection picklists - supporting multiple values
You can map the resource field to a long text field or to a multiple-selection picklist. This is the most flexible option as it allows multiple resources for the same event without triggers or other customizations. This is a great option when you're mocking up a new calendar to play around with DayBack.
For text fields, you'll leave the switch for "My Resource is a Related Field" set to "no."
Lookups and related records - my resource is a related field
Resource Name Field - DayBack will fill in the Name field of your object by default. But you can change this to another field in the object if you'd prefer. For example, you may create a formula field that combines the contractor's name and specialty: you could show that instead of the contractor's name. Note that if you change or create fields in other Salesforce screens while you have this field mapping screen open, you can click the button "Refresh Drop-Down Options" at the top of the screen to get access to newly created fields.
Label - Enter the text you'd to see to the left of the resource name in DayBack's popover when you click on an event in the calendar.
Searching for and Selecting Resources
Scroll down on the resources tab and you'll see a section for "Searching for and Selecting Resources." DayBack" completes this section for you as soon as you select a Resource ID Field Name above.
The only changes you may want to make here involve the "search field" and "display field" -- leave the other options alone.