Mapping the Resource Field in FileMaker

Text Fields

Mapping the resource to a text field is the simplest and most versatile option since it easily supports assigning multiple resources to the same event. In fact, if you're just starting to use DayBack, you may want to make a simple text field for the resource so you can see how DayBack works and then come back and swap that for a calculated field or related field later.
It's important that the text field be editable so your users can drag events from one resource to another to reschedule them. You can use an auto-enter as long as the field is editable.

Using Related Records for Your Resources

Sometimes your event will simply contain the ID of a resource, but DayBack will be looking for the name of that resource. The resource field you map to in DayBack must be local to the event's table, so you can't map to the related field directly. In this case, you'll create a calculated field or an auto-enter calc to bring the related resource's name (or names) into your event. 

But when you edit the event, you'll want DayBack to edit the ID, not the name you've mapped, so you'll follow the same instructions as in the calculated field section below to teach DayBack to edit something besides the fields you actually mapped. 

Calculated Fields

You can map to calculated fields for your resource as long as you tweak DayBack's FileMaker scripts so they know not to try and edit the calculated field. Learn more here: Using Calculated Fields for Status or Resource in FileMaker

Mapping to a calculated field can be handy when you want your resource to show a combination of two other fields: in a school, for example, your resource could be a calculated field adding a room name and a teacher's name, separated by a carriage return.