SeedCodeComplete3

Troubleshooting

FileMaker 19: Changes Required

Claris changed some things in FileMaker 19 that introduced some new issues with DayBack Classic. If you'd like to use your DayBack Classic calendar in FileMaker 19, you'll need to be running build 10.61 or later.

Instructions on getting your calendar updated here: In App Updates

FileMaker 16: Changes Required

If you're seeing this error when you first open DayBack in FileMaker 16...

...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs.

URL Issues, or the Calendar Seems to be Opening an Older Copy of FileMaker

The calendar uses the fmp url protocol to call scripts in your file. Some computers can get confused as to which copy of FileMaker to use in responding to these url calls. Symptoms can include the calendar showing no events, or launching another copy of FileMaker on startup.

Here is a test to make sure the URL protocol is working properly in your version, along with instructions on how to fix it: FMP URLs

If you recently applied the script updates for build 10.50, and you used FileMaker Pro 16 or earlier, you'll see a blank web viewer and receive the FMP URL when opening the file with FileMaker 17+. To fix this, open the file in FileMaker 17+ and change the "Create folders" option to "On" in the Export Field Contents step on line 18 of the "Set Temp Path Folder" script.

No events appearing on the calendar?

If you can't see any events in the calendar after your integration, here are a few things to check.

Note that Event Colors have their own trouble shooting section here.

1. Do you have any other versions of FileMaker open? The calendar utilizes the FMP URL protocol. When multiple versions of FileMaker are open at once this protocol may target the wrong version and scripts will not fire in the version where the DayBack file is open. Just close the other open FileMaker apps and everything should work as expected. Or see our article on FMP URLs to test that they are working

2. Make sure your filename doesn't include an ampersand (&). DayBack uses FMP URLs for querying FileMaker data from the WebViewer and the ampersand character is used for separating parameters. A DayBack filename including an ampersand will result in the error message, 'The file "DayBack.fmp12" could not be opened...' and no events will be loaded.

3. Run the "Upon Opening" script again.

4. Double check the calc fields you added to your events table, especially "DBk_WebViewerSource". If they begin /* then they're "commented out" and you need to remove the leading /* and trailing */ before the fields will work. If this is the case you'll likely need to replace our "sample" fields with your own once you remove these characters and try to save the field.

5. Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp calc fields show a valid number like 63611269200? (If not, skip to number 6 below.)

6. Check your system's date formats. If you're using a customized date format switch to one of the standard formats like United Kingdom and then close and re-open FileMaker. It is unusual, but stray characters in the date format can screw up the calendar. If switching formats repairs it, slowly add your customizations again checking that the calendar continues to recognize them.

7. Take a look at the date and time fields you're using in the timestamp fields you pasted into your events table: are these defined as date and time respectively, or are they text. (Text will not work.) Also, make sure these timestamp calcs reference the same date and time fields you've mapped to on your Source No X layout. So if you're using a field called "Start Date" on Source No 1, make sure the time stamp calc uses "Start Date" and not something else like "Order Date". (Later, you can make a different source for Order Date.) This is especially something to look at if you have more than one source; if the sources are using different date and time fields they'll need different timestamp calcs.

8. A few things in the calendar use cookies in order to work properly--things like remembering the sidebar's visibility setting for the current user. You may want to check that cookies aren't disabled in your default browser.

9. Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.

10. Try changing the BuildNumberCalc field in the CalendarInterface table from a global to an unstored calculation. This can help if you've integrated DayBack into your own file while your file was hosted in FileMaker Server.

11. If your file is set up to auto-enter an account that does not have access to the event data, and it is being hosted in FileMaker Server, and you are using Perform Script on Server (PSOS), your users might not see any data on the DayBack UI. This is because when scripts run on the server they use the auto-login account to query the events table. The solution is to add a "Re-Login" step in your OnFirstWindowOpen script so PSOS will always use the Admin account. Wrap this in an If[] condition with the following formula:

PatternCount (Get(ApplicationVersion); "Server")

12. A similar PSOS issue: if you're using Record Level Access and some of your access rules depend on global fields or variables, these are likely not being respected in PSOS sessions. Turn PSOS off (instructions are here to see if your events show up. If they do, you'll need to set these variables as part of your OnFirstWindowOpen script so they're present in the data file when DayBack runs scripts there. Then turn PSOS back on.

13. Rarely, some months may appear to have all events missing, caused by a lone backslash "\" in one of your event records. If an event field ends in or contains only a backslash, removing this character or adding another character after it will correct the issue.

14. A few users have experienced events not loading when running an older version of MacOS Sierra (10.12.5 or below) and FileMaker 16. Upgrading the Operating System should resolve this issue.

15. If you're modifying the CalendarColors table directly in any way, instead of using DayBack's built-in sidebar to manage status colors, verify that each record in this table has a value in the "Name" field. Any empty values in the "Name" field will result in the calendar not being able to load any events.

Event popover blank / contents not loading

Some users of MacOS High Sierra have experienced a completely blank popover in DayBack. This seems to be an issue with earlier builds of High Sierra and can be fixed by making sure you have installed the latest updates to the OS.

This can also happen if your computer goes to sleep or hibernate while the file is open. DayBack exports files to the FileMaker temporary directory that are used for the calendar, and the connection to the temporary directory is broken when the computer sleeps. To prevent this, you can change your computer's settings to not go to sleep or hibernate. As an alternate workaround, you can close and re-open the file or run the "Upon Opening" script to re-establish the files in the temporary directory.

Custom Button Action / Additional Fields buttons are missing

If the buttons to open the custom button action or additional fields drawers are missing from your popover, it's likely that you've applied in-app updates to your instance of DayBack, but haven't applied the required script updates (specifically from build 10.44). When applying in-app updates, make sure you apply all of the required script updates, from the build you're on, to the latest, as detailed in the version history page here.

Errors when Editing Events

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

Error 102

102 means a "field is missing" so it sounds like DayBack is trying to write your event back to FileMaker but can't find one of the fields it needs. This is probably because one of the fields on the Source No X mapping layout got skipped or deleted.

I'd revisit that "Source No..." layout (probably "Source No 1" unless you're integrating additional sources) and check each tab to make sure the fields are mapped to fields in your table. If everything looks good you might then compare this layout with that in a fresh download of DayBack to make sure none of the fields were deleted from the layout. If they were, copy and paste the field from the clean copy and then point it at the relevant field in your table.

Error 103

"Relationship is missing." Double check to make sure the table occurrence name for your calendar source matches the $$sc_SourceTableOccurrenceName variable set within the "Load Source Settings at Startup..." script. The value in that variable may be matching a table occurrence on DayBack's relationship graph -- just not the correct one for this source.

Error 201

"Field Can't Be Modified." Make sure that all of the fields you mapped on the "Source No 1" layout are writable; that is, not calculation fields. If you are using a calc field for any of those fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead. (The most common cause of 201 errors is mapping a calculated field to the event Summary. You'll want to make sure the field mapped there is editable.)

Calendar not loading

If you've embedded the calendar or implemented the script updates for build 10.50 using a version of FileMaker earlier than 17, and are now having issues opening DayBack in FileMaker 17+, there's likely a script step that needs updating. Using FileMaker 17+, verify that the "Create folders" option of the "Export Field Contents" step on line 18 of the "Set Temp Path Folder" script is toggled "On". Close and re-open the file, or run the "Upon Opening" script for the changes to take effect.

Lists in FileMaker require that you have at least two items to be considered a value list. In older builds of DayBack, in the $$sc_CustomEventActions variable, we leave an empty string ("") as the second list item to account for this. If you've recently made changes to the custom actions of a source and you only have one custom action, make sure you've left the extra empty list item in there so that the list is complete.

If you've integrated DayBack 9.42 or earlier into your hosted solution, the problem may be due to the "global" storage setting on the "BuildNumberCalc" calculation field in the CalendarInterface table. Fortunately the fix is easy; simply remove the global storage option on that field.

After adding a new source, the calendar won't load

DayBack needs to load sources in numerical order without skipping numbers. So if your "Load Source Settings at Startup" script is set up to only load sources 1 and 3 (for example, you've disabled the sample ToDoList source), then the calendar will not load properly. To resolve this, make sure your active source numbers don't skip numbers. For your new source, you'll likely need to

1. Rename your Source No layout,

2. Change the sc_sourceNumber value in the DBk_WebViewerSource field,

3. And change the $sc_SourceNumber value for this source within the "Load Source Settings at Startup" script.

Can't link contacts or projects

There are a couple of fields you need to add to your contact and project tables and it can be easy to overlook these--or the fields may be there but be commented out (that is, they may begin with /* and end with */). The fields are described here, please take a moment to make sure they're in your contact or project table and that they're returning data (ie add the fields to a layout and look at the fields in browse mode). If they're not returning data it's likely that the calcs are commented out: uncomment them and follow the instructions inside each calc to point it at the correct fields in your contact or project.

Losing custom translations or CSS themes

Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, if the CalendarInterface record is deleted, or if a new record is added to the CalendarInterface table. To prevent this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.

I'm seeing "Summarizing..." when the calendar loads

If you see "Summarizing Field "DBk_WebViewerEventData" it could be because you're returning a TON of data from FileMaker. You'll find more about this and strategies to slim down your event payload as the last section on the page here: Speed.

I'm seeing "Host Capacity is Exceeded" warnings

If you see a FileMaker warning that the "Host Capacity is Exceeded" when loading the calendar, and DayBack is hosted on a FileMaker Server, it's possible your Server's scripting engine has stopped. To quickly get past this issue, you can disable DayBack's use of PSOS by editing the first Set Variable step in the "Load Calendar Settings - On Startup..." script. You can also restart your server's "fmse" component using the command line on the host machine to get the scripting engine running again and continue taking advantage of PSOS in DayBack.

The command is fmsadmin restart fmse -y

Can't enable PSOS on FileMaker Cloud

Check out the solution here

The Event Detail window hangs after it's closed

In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve this, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. Users should not notice these adjustments, but the calendar will redraw so that the event window is fully cleared away!

I'm seeing "The calendar is meant to run in the main solution window only"

This warning is meant to fire if you try to make a second calendar window, but can also come up if you're renaming the calendar window after DayBack's Upon Opening script has run.

There is a script step at the beginning of DayBack's "Upon Opening" script (at line 18) that records the current window name being used for the calendar: it sounds like you've renamed the window *after* that script ran. Just return there and use the Upon Opening script to set the window name you want to use (at line 15) and you should be all set.

Setting selections aren't retained when leaving the calendar on Windows

On windows FileMaker does not retain cookies or local storage items in the webviewer. This is a limitation that is present when Internet Explorer is not open. If Internet Explorer is open while using DayBack on windows then cookies are available and can be used to store settings for that session.

We have created a simple command for determining if Internet Explorer is not open, if it is not open then IE will be launched hidden. To add this behavior to your file follow the directions below:

Create a new script called "Launch IE"

In this new script add a "Send Event" script step, and select the "text" option. Then paste the code below in the text box:

cmd.exe /c tasklist | find "iexplore.exe" || start /B /MIN iexplore.exe

It should look like this:

Wrap the send event script step in an if statement so we only run this command in Windows. The if statement will evaluate:

Abs ( Get ( SystemPlatform ) ) = 2

Then you can choose to either run this script at startup or as a script trigger "OnLayoutExit". Running on startup is great as then it only runs once, be aware that if a user closes IE during the use of the calendar saving settings for the session will no longer work. So we recommend a combination. Run the script on startup to make sure IE is open. Then add a script trigger to the "Calendar" layout to run the script for "OnLayoutExit". To ensure IE has time to fully launch please add a "Pause/Resume" script step for 2 seconds at the end of the "Launch IE" script inside the if statement as shown in the image above.

Excessive memory use in FileMaker for Windows 16+

There is a reported issue in FileMaker for Windows 16+ with garbage collection when refreshing/reloading WebViewers. This means that every time a WebViewer is refreshed, additional memory is used for the FileMaker process until the program is closed. This usually is not an issue on most computers, but those with limited memory (RAM) may experience performance drops.

Unfortunately, there isn't a fix for this issue, but rather a workaround of closing FileMaker and re-opening your solution.

If you experience this issue and would like to encourage a fix from FileMaker, we encourage you to Give Feedback or view the reported issue.

Yellow script warning when opening calendar in Windows

When opening the calendar layout, you see a yellow bar warning you: "To help protect your security, Internet Explorer has restricted this webpage from running scripts..."

This warning is shown from Internet Explorer to notify you that the page (DayBack) is trying to run scripts (JavaScript) to load the page. You can click this warning and allow scripts to run, but this will only be retained for the current WebViewer session. If the calendar layout is re-loaded, it will again show the warning.

There are 3 possible causes of this warning that we have been able to verify:

• IE Security Settings - Your Internet Explorer security settings may be preventing scripts from running in pages. To fix this, you'll want to open the IE settings, go to the Advanced tab, and check the option for "Allow active content to run in files on My Computer" option. A restart of the computer is required for this change to take effect

• FileMaker Trial Version - If you're running a trial version of FileMaker, this can sometimes be the cause of this error. If this is the cause of the issue, a licensed version of FileMaker should resolve it. Some users have noted that entering the license info into an already installed trial version does not fix this issue, so you'll need to fully uninstall FileMaker, then re-install FileMaker, entering your license details during setup.

• Windows 7 Remote Desktop / Terminal Services users - Some users of Windows 7 through Remote Desktop Services have reported this issue and haven't been able to resolve it with the above two solutions. In this case, unfortunately, the only option is to acknowledge the script warning and allow scripts to run when loading the calendar.

Windows and high DPI screens

On Windows systems with a smaller screen and a high DPI (resolution), the calendar text and objects may display very small and unreadable. There are a couple of options to address this, some of which are easier than others.

• Since WebViewers are rendered as a web page, they have a separate zoom mechanism from FileMaker's zoom. This means you can zoom into the calendar using ctrl+scroll (or + and -) and it will not affect the other FileMaker objects. This is probably the easiest way to get the calendar objects to render at a higher scale without making your Event Detail window look too large.

• You could try increasing the system-wide Windows DPI scaling, keeping in mind that this will have an effect on all apps. Here's a link to instructions on adjusting the Windows DPI scaling: https://technet.microsoft.com/en-us/library/ff629368.aspx?f=255&MSPPError=-2147217396

• You could add the following to your CSS theme to adjust the zoom for Windows devices with high DPI screens:

@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;

}

This will only apply to Windows devices with screens showing 180dpi (dots per inch) or higher. You might want to modify the 3 dpi settings (1.8, 18/10, 180dpi) to get the right criteria for when to zoom or not.

For example, on a 40" 4k screen, DayBack looks great by default, so you don't want to resize on that screen. The dpi on this screen is 110.

An 11" 1080p screen has a dpi of 200, so you probably would want to zoom in, but it's going to take some trial and error to get the right number.