FileMaker WebDirect

Can you use DayBack with WebDirect?

Yes! If you're using DayBack 19, there's no special setup required to make DayBack work in WebDirect. Simply open the layout and use DayBack as you normally would in the FileMaker client. If you're using DayBack Classic, regardless of the FileMaker version, please refer to the information below.

Using DayBack with Earlier Versions of FileMaker

If you haven't upgraded to DayBack 19, you can still use DayBack Classic in WebDirect. However, you'll need to set up your calendar as a FileMaker Custom Web Publishing (CWP) source. This process is more complex and offers fewer features, so we recommend upgrading to DayBack 19 instead.

Setting Up DayBack in WebDirect

Once you've set up your calendars, simply add a web viewer to your layout and use the DayBack Online URL as the web address: https://app.dayback.com.

After verifying that it's working, you may want to add a user token to the URL so that DayBack can remember you, eliminating the need to log in each time.

Recommended optimizations to your web viewer:

  • Ensure there is no border around it.
  • Check in the inspector that there is no padding.
  • Turn on all four autosizing anchors to allow the web viewer to grow and fill your layout and screen.

Remember, the web viewer doesn't need to be the only element on your layout. Navigation elements can be placed to the left or above the web viewer containing DayBack. Integrating DayBack with FileMaker elements in this way can create a seamless experience within your FileMaker solution.

Here's an overview:

You can also use custom actions to interact with the calendar and trigger scripts in other online services, including WebDirect. Examples of the URL formats used in custom actions can be found in our custom action examples.

If you've also integrated DayBack Classic

If you've integrated DayBack Classic for your FileMaker Pro users, ensure that the "Upon Opening" script for DayBack Classic does not run during startup for your WebDirect users. Running this script in WebDirect can cause errors. To prevent this, add the following steps at the beginning of the "Upon Opening" script:

	If [Get(SystemPlatform) = 4]
		Exit Script []
	End If

This check will exit the script if it detects that the user is on a WebDirect platform, avoiding any issues.