Troubleshooting DayBack for FileMaker

General Troubleshooting

Times down the left-hand side are all random like 10:08

Visit "Time Scales" in the left-hand sidebar of Admin Settings and you've likely entered an odd time into one of the settings like "earliest time visible". These values should be in the form HH:MM:SS like 06:00:00 for 6am. If you enter 06:07:00 you'll see odd results.

DayBack Won't Load

There are two FileMaker scripts that may help. Run one or both of these if you just see the blue loading bar but no calendar:

Go to Admin Settings - DayBack  This will take you to admin settings and reset the web viewer.

Sign Out - DayBack  Signs you out and takes you back to the sign-in page. More: how to sign out with a FileMaker Script.

If you believe the loading problem is because you've been writing custom app actions that may not function, here's how to get DayBack to bypass them: close the FileMaker file and re-open it while holding down the shift key and moving the mouse back and forth as you arrive at the calendar layout. This will take you straight to DayBack settings where you can turn off your app action by unchecking the box next to "app" below the action.

DayBack "Can't find a mapped field or custom field"

If your setup is passing field validation in DayBack, but you're still seeing this red error at the bottom of the calendar, please check these three things:

• Make sure any disabled fields are also unmapped (set to a blank value instead of a real field).
• Confirm that the context selected for your DBk_JSON calc field is the same table occurrence name as the table occurrence name you specified for this calendar in DayBack settings "Calendar Info".
• Make sure the table occurrence name in DayBack settings "Calendar Info" is the same in “both” files if DayBack is linked (vs embedded) or if the data is in another file. In other words, your local table occurrence and original table occurrence should have the same name.

DayBack "Cannot set the field ::DBk_Timestamp..."

This error means DayBack wasn't able to set this field in find mode on the calendar source's specified layout. This could be caused by one of the following reasons:

• The layout specified doesn't have Quick Find enabled, doesn't allow entering a value into the field specified in the error, or has script triggers that are interfering with the DayBack scripts to query the data.
  
  Your layout should not have any script triggers and doesn't need to have any fields on it. You can use the "Sample Events" layout in the stock DayBack file as a reference for how your layout should be set up.
• The FileMaker scripting engine may have run into an issue and need to be restarted. This is usually the case if you're receiving the same error on multiple calendars. Restarting the scripting engine can be done by stopping and starting the database server, or by entering the following command line prompts to restart just the scripting engine on the server:
  
  

  	fmsadmin stop fmse
  	fmsadmin start fmse<br>
  	

I'm Seeing Two of Each Event

If you've created any App Actions, check that the action's "Prevent Default Action" is set correctly. If that's set to NO and your action is using action.callbacks.confirm(); you're essentially telling DayBack to render the calendar twice.

The Event Popover is Blank

There is a known issue in FileMaker web viewers on Mac: if you maximize or restore the window, you'll need to reload the web viewer or change layouts for the web viewer to resume working correctly.

The Calendar is Blank (or one Source is Blank)

The most common cause of events not showing up is that you have some filters applied and no events match those filters. If you're filtering for a particular status (or calendar, or resource) and then create a new appointment with a different status, that event will disappear since it doesn't match the filters you have in place. Clicking "Clear filters" at the bottom of DayBack's filters tab in the left-hand sidebar will bring these events back if that's the case. If that doesn't help, try these ideas...

Double Check Your Field Mapping

Go to admin settings and select the calendar you're interested in. On the Calendar Info tab, click "Validate Layout" and "Validate Table Occurrence". Click on the Field Mapping tab and scroll all the way down: click "Validate Field Mapping," correcting any issues you see.

Check for calculation fields that are commented out.

When copying the required calculation fields to your file, if your table doesn't have one or more of the referenced fields, FileMaker will comment them out with a /* at the beginning and a */ at the end of the calculation. You'll need to remove these comment markers and then update all of the referenced fields to point to the appropriate fields in your file.

Mapped date field is empty.

DayBack will only show an event on the calendar that has a valid start date. Make sure your events have a date set in the field you've mapped to the start date in DayBack.

Incorrect Contact or Project Table Occurrence Names

If your events are linked to contacts/projects AND your events table is in a different file than the file DayBack is in, be sure the contact and project table occurrence names in DayBack are the same names those table occurrences have in your events file. If you change the table occurrence names in DayBack, be sure to change the names used in Field Mapping and Related records. More details here: Setting up Contacts & Projects.

FileMaker Errors when Editing Events

Some tips for errors you might see when dragging events around or editing them...

@media only screen and (-webkit-min-device-pixel-ratio: 1.8),
only screen and (-o-min-device-pixel-ratio: 18/10),
only screen and (min-resolution: 180dpi)
{
	@-ms-viewport{
		width:960px;
	}
}
<br>