Multiple Resources per Object
Can I select more than one resource for the same item?
Yes, provided your data model in Salesforce or FileMaker supports that.
You can drag an event on the Resource views from one resource column/row to another. When you do, the new resource will be swapped out for the one you dragged from. Other resources for the event remain intact.
See this in action here: Assigning Multiple Resources to an Item.
Multiple Resources in Salesforce
Do Salesforce records support more than one resource per item?
Yes, depending on the Salesforce object you're using.
If you're using the native Events object, the default resource mapping to Owner Name won't allow multiple values because Salesforce only permits an item to have a single owner. Mapping to a custom text field in Events will work.
But if you've mapped to another object with a custom field set up as either a long text field or a multi-select picklist, then you'll be able to select more than one resource by shift-clicking resources in DayBack's resource drawer (screenshot below). For more on field mapping, check this out: Mapping the Resource Field in Salesforce.
Can I treat both people and rooms as resources?
Absolutely-- this is one of the most common setups for DayBack. How you set this up will depend on where the resources are recorded in your Salesforce object.
Some of my objects use "owner" for a person, and some use another field for "room"
(My objects each have one resource field) This setup requires no special configuration, though you'll likely want to create a resource folder for people and another for rooms. If the field you're using for "room" is a long text field or a multi-select picklist you'll be able to associate multiple resources with the same item.
Within the same object, one resource is the activity owner, the other is a custom field for "room"
(One of my objects has two resource fields) In this scenario, you'll create two calendar sources mapped to the same table: one will use the owner as the resource field and the other source will use the room. You can then turn on the first source (let's say you've named it "Activities by Technician") to view your assignments by person, and show just the second source ("Activities by Room No.") to view them by room. Again, you'll likely want to create a resource folder for people and another for rooms.
My resource is a long text field or a multi-select picklist that can support multiple values
(My object has one resource field that will contain more than one entry) This is by far the simplest setup and the easiest for users when they are working with the schedule. In the event popover, users can simply shift-click when selecting resources for an item to associate more than one resource with it. In your resources field, these multiple resources will be written as a semicolon-separated list in your Salesforce object's resource field just as if they were entered in your picklist.
You can drag an event on the Resource view from one resource column to another; when you do you'll be swapping out the new resource for the resource you dragged from. Other resources for the event remain intact.
Multiple Resources in FileMaker
Simply shift-click when selecting resources for an event to associate more than one resource with the event. In FileMaker, these multiple resources will be written as a return-separated list in your FileMaker table's resource field.
What if I'm using the ID instead of the resource name to link resources and events?
DayBack requires the field you've mapped to "Resource" to be the name of your resource, but if you're using IDs as well, you can set up your ID field to lookup the resources' IDs based on the names entered in the field you've mapped to "Resource". Learn more here: Mapping the Resource Field in FileMaker.
Multiple Resources in Google Calendar
You don't need to do anything to get multiple resources to work in Google Calendar. DayBack essentially lets you add new fields to Google Calendar, and Resource is one example of that.
DayBack currently supports multiple resources (and a single status) per Google event.