Troubleshooting
DayBackOnline.Troubleshooting History
Show minor edits - Show changes to output
Changed line 37 from:
-> Once you're getting something more than 1 byte returned in test details or results at the url above you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct. If the URL tests above are passing but you still can't get the PHP file to work AND you're sing "localhost" in your PHP file, it could be that your server / hosting provider has settings preventing that: try replacing "localhost" with your server IP address.
to:
-> Once you're getting something more than 1 byte returned in test details or results at the url above you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct. If the URL tests above are passing but you still can't get the PHP file to work AND you're using "localhost" in your PHP file, it could be that your server / hosting provider has settings preventing that: try replacing "localhost" with your server IP address.
Added lines 6-9:
!! General Improvements
FileMaker Web Publishing will pull data from every field on your layout, even though DayBack only needs some of the fields in your table. So to speed up your queries, ''and'' to reduce the possibility that bad data is getting sent to DayBack, be sure that the layout specified in DayBack admin's Source Settings only contains the fields DayBack requires.
November 17, 2017, at 06:02 PM
by - Added tip section on PHPRelay file check
Added lines 30-31:
-> '''Tip:''' If you're not getting the correct expected output, such as file not found or a 500 error, try replacing your PHPRelay file with the downloaded, untouched version. If that works, then your PHP service is functioning correctly. Make sure you've used a plain text editor, as mentioned in our docs [[PHPrelayFile#TextEditor | here]]. Also, verify that there aren't any commas or quotes that have been accidentally deleted where the file was edited.
October 30, 2017, at 11:31 PM
by - Added Error 4 issue with TimeStampNum Calc End field
Added lines 40-41:
-> The TimeStampNum Calc End field is required to be mapped, even if you've disabled it in the settings. If you don't enter a valid field, you will receive the following error when loading the calendar: "There was an error retrieving FileMaker events: 4 - Command is unknown"
Changed line 31 from:
-> Once you're getting something more than 1 byte returned in test details or results at the url above you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct.
to:
-> Once you're getting something more than 1 byte returned in test details or results at the url above you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct. If the URL tests above are passing but you still can't get the PHP file to work AND you're sing "localhost" in your PHP file, it could be that your server / hosting provider has settings preventing that: try replacing "localhost" with your server IP address.
Changed line 29 from:
-> That should return the phpinfo on your server if the relay is in the right spot and php is running. Remember, if you connect to dayback.com over https and your php relay / fmserver is only on http then you will get that error that it couldn't connect to the php relay file. So if your relay file is http you need to go to https://app.dayback.com
to:
-> That should return the phpinfo on your server if the relay is in the right spot and php is running. Remember, if you connect to dayback.com over https and your php relay / fmserver is only on http then you will get that error that it couldn't connect to the php relay file. So if your relay file is http you need to log into https://app.dayback.com instead of https://app...
Changed line 29 from:
-> That should return the phpinfo on your server if the relay is in the right spot and php is running.
to:
-> That should return the phpinfo on your server if the relay is in the right spot and php is running. Remember, if you connect to dayback.com over https and your php relay / fmserver is only on http then you will get that error that it couldn't connect to the php relay file. So if your relay file is http you need to go to https://app.dayback.com
Changed lines 25-27 from:
-> If you get results in the test above and see your file listed there but got "0" or "1" byte downloaded in your test details, then your PHPrelay file is in the wrong place. Double check that the location is one of the ones listed [[PHPrelayFile | here]] in "Where does the file go?"
-> Once you're getting something more than 1 byte returnedtest details you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct.
-> Once you're getting something more than 1 byte returned
to:
-> If you get results in the test above and see your file listed there but got "0" or "1" byte downloaded in your test details, then your PHPrelay file is in the wrong place. Double check that the location is one of the ones listed [[PHPrelayFile | here]] in "Where does the file go?" You can test that you have the relay in the correct location by entering this url:
--> https://serverAddress/fmxjRelay.php?test=true
-> That should return the phpinfo on your server if the relay is in the right spot and php is running.
-> Once you're getting something more than 1 byte returned in test details or results at the url above you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct.
--> https://serverAddress/fmxjRelay.php?test=true
-> That should return the phpinfo on your server if the relay is in the right spot and php is running.
-> Once you're getting something more than 1 byte returned in test details or results at the url above you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct.
Changed line 25 from:
-> If you see your file listed there but got "0" or "1" byte downloaded in your test details, then your PHPrelay file is in the wrong place. Double check that the location is one of the ones listed [[PHPrelayFile | here]] in "Where does the file go?"
to:
-> If you get results in the test above and see your file listed there but got "0" or "1" byte downloaded in your test details, then your PHPrelay file is in the wrong place. Double check that the location is one of the ones listed [[PHPrelayFile | here]] in "Where does the file go?"
Added lines 66-73:
-> '''Error 500'''
--> "There was an error saving the event and your changes will be reverted: 500 - Date value does not meet validation entry options." When you see this it likely means that the Date Format in your Source Settings doesn't match that in your file. To begin with the format needs to be all capital letters like MM/DD/YYYY. To be sure the setting here matches your file, click on "Test Source Settings" then "Show Test Details" and scan down through the results until you find "Fields Available on Layout..." below that you'll see the date format of your file. it likely looks like this:
---> "DATEFORMAT": "MM/dd/yyyy"
--> Then make sure that the settings you've entered into DayBack are the uppercase version of the format you find here.
Changed lines 14-15 from:
to:
-> If you get an orange failed sign for the PHP Relay file it likely means your [[PHPrelayFile | PHPrelay]] file isn't there or is in the wrong place. It could also be that php isn't running on your FileMaker Server.
-> If you get an orange failed sign that says the DayBack account doesn't exist in your PHP Relay file it likely means that you have set the variable "$loginByName" to true in PHP Relay file and there is not a match for the DayBack account in the if statement to determine the correct FileMaker account.
-> If you get an orange failed sign on the FileMaker file there are a few things to check.
Changed line 61 from:
--> If you are using a calc field for any of the other fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead. You might also check that the account you've set up in the [[PHP relay | PHPrelay]] uses a privilege set that has write privileges to all the fields you mapped.
to:
--> If you are using a calc field for any of the other fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead. You might also check that the account you've set up in the [[PHPrelayFile| PHPrelay]] uses a privilege set that has write privileges to all the fields you mapped.
Added lines 46-61:
!! 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 Online 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 you've mapped got removed from the layout you specified or the field got deleted from your table.
--> I'd return to Source Settings and re-run the tests towards the bottom of the page to see which field(s) this might be. You can also revisit layout you specified (probably "Source No 1" if you're using DayBack for FileMaker also) and make sure the fields are mapped to fields in your table.
-> '''Error 201'''
--> "Field Can't Be Modified." Make sure that the fields you mapped are writable; that is, not calculation fields. Of the fields DayBack Online asks for, only the three that have "calc" in the name may be calculated fields.
--> If you are using a calc field for any of the other fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead. You might also check that the account you've set up in the [[PHP relay | PHPrelay]] uses a privilege set that has write privileges to all the fields you mapped.
Changed lines 17-25 from:
-> If all that looks good, check the test details to see, for example, that the file name you entered is one of the file names on your server. Only files with XML web publishing enabled show up, so make sure it's enabled for your file.
to:
-> Begin by testing to make sure XML web publishing is running. You can do this by manually typing the following into your browser, replacing "serverAddress" with the server address you entered in DayBack's configuration:
--> https://serverAddress/fmi/xml/FMPXMLRESULT.xml?-dbnames
-> If you see your file listed there but got "0" or "1" byte downloaded in your test details, then your PHPrelay file is in the wrong place. Double check that the location is one of the ones listed [[PHPrelayFile | here]] in "Where does the file go?"
-> Once you're getting something more than 1 byte returned in test details you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct.
-> Check the test details to see, for example, that the file name you entered is one of the file names on your server. Only files with XML web publishing enabled show up, so make sure it's enabled for your file.
--> https://serverAddress/fmi/xml/FMPXMLRESULT.xml?-dbnames
-> If you see your file listed there but got "0" or "1" byte downloaded in your test details, then your PHPrelay file is in the wrong place. Double check that the location is one of the ones listed [[PHPrelayFile | here]] in "Where does the file go?"
-> Once you're getting something more than 1 byte returned in test details you'll have the PHPrelay file in the right place and can make sure the rest of your configuration is correct.
-> Check the test details to see, for example, that the file name you entered is one of the file names on your server. Only files with XML web publishing enabled show up, so make sure it's enabled for your file.
Changed lines 37-41 from:
-> If you're not seeing colors it's because the field you've mapped doesn't contain one of the status values in the sidebar.
to:
-> If you're not seeing colors it's because the field you've mapped doesn't contain one of the status values in the sidebar.
----
None of that help? Don't hesitate to %newwin% [[https://www.seedcode.com/contact/ | get in touch]].
----
None of that help? Don't hesitate to %newwin% [[https://www.seedcode.com/contact/ | get in touch]].
Changed lines 23-24 from:
to:
-> If you have green lights on your tests but no events I'd check the fields mapped to the "TimestampNum calc start" and "...end" fields. Are these calcs defined to return numbers? Note that if your paste in our example field definition you need to point parts of the "Let" statements at your own date and time fields: double check that you picked the right fields from your table.
Changed lines 27-37 from:
to:
-> This likely means that your "TimestampNum calc start" and "...end" fields described above are returning numbers but the calcs themselves aren't correct or only one of them is (only the start or end calc).
'''I can see bars for my events but no text'''
-> Double check the field mapped to "Event display calc" and make sure it's returning a value on your FileMaker layout.
'''None of my events have any colors'''
-> You'll see event colors when the values in the field you've mapped to "Status" match the values in the calendar's Status Filters (these are on the Filters tab of the calendar sidebar).
-> If you're not seeing colors it's because the field you've mapped doesn't contain one of the status values in the sidebar.
'''I can see bars for my events but no text'''
-> Double check the field mapped to "Event display calc" and make sure it's returning a value on your FileMaker layout.
'''None of my events have any colors'''
-> You'll see event colors when the values in the field you've mapped to "Status" match the values in the calendar's Status Filters (these are on the Filters tab of the calendar sidebar).
-> If you're not seeing colors it's because the field you've mapped doesn't contain one of the status values in the sidebar.
Changed lines 9-21 from:
My server settings test aren't doing anything
clicking
My server settings test are failing
My server settings test passed but I can't see any events
I can see some events but they're all on the wrong date or for multiple days
My server settings test are failing
My server settings test passed but I
I can see some events but they're all on the wrong date or for multiple
to:
'''My server settings test aren't doing anything'''
-> If you click "Test Source Settings" and don't get any results, it is likely because DayBack can't see your FileMaker Server at all. Check that the server address is correct, and that %newwin% [[https://fmhelp.filemaker.com/docs/14/en/fms14_cwp_guide.pdf | XML Web Publishing]] is enabled for your server.
'''My server settings test are failing'''
-> If you get orange failed signs for all tests, click on test details. If you see "0 bytes downloaded" it likely means your [[PHPrelayFile | PHPrelay]] file isn't there, is in the wrong place, or doesn't have the correct access privileges to log into the FileMaker file you specified. It could also be that php isn't running on your FileMaker Server.
-> If all that looks good, check the test details to see, for example, that the file name you entered is one of the file names on your server. Only files with XML web publishing enabled show up, so make sure it's enabled for your file.
-> Same thing with layouts: check the test details to see which layouts DayBack can see in your FileMaker file. It's likely that your spelling is wrong (remember that these entries are case sensitive).
'''My server settings test passed but I can't see any events'''
coming soon
'''I can see some events but they're all on the wrong date or for multiple days'''
coming soon
-> If you click "Test Source Settings" and don't get any results, it is likely because DayBack can't see your FileMaker Server at all. Check that the server address is correct, and that %newwin% [[https://fmhelp.filemaker.com/docs/14/en/fms14_cwp_guide.pdf | XML Web Publishing]] is enabled for your server.
'''My server settings test are failing'''
-> If you get orange failed signs for all tests, click on test details. If you see "0 bytes downloaded" it likely means your [[PHPrelayFile | PHPrelay]] file isn't there, is in the wrong place, or doesn't have the correct access privileges to log into the FileMaker file you specified. It could also be that php isn't running on your FileMaker Server.
-> If all that looks good, check the test details to see, for example, that the file name you entered is one of the file names on your server. Only files with XML web publishing enabled show up, so make sure it's enabled for your file.
-> Same thing with layouts: check the test details to see which layouts DayBack can see in your FileMaker file. It's likely that your spelling is wrong (remember that these entries are case sensitive).
'''My server settings test passed but I can't see any events'''
coming soon
'''I can see some events but they're all on the wrong date or for multiple days'''
coming soon
Changed line 5 from:
%newwin, width=400% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
to:
%center% %newwin, width=400% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
Changed line 5 from:
%newwin, width=400% %center% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
to:
%newwin, width=400% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
Changed line 5 from:
%newwin, center, width=400% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
to:
%newwin, width=400% %center% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
Changed line 5 from:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
to:
%newwin, center, width=400% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
Changed line 5 from:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonlne/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonlne/SettingTests.png]]
to:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SettingTests.png]]
Changed lines 1-14 from:
!! 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 folks computers can get confused as to which copy of FileMaker to use in responding to these url calls. Fortunately this is pretty easy to fix.
-> '''Mac''' There is a free preference pane you can download that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install [[https:/www.rubicode.com/Software/RCDefaultApp/ | this preference pane]] (once downloaded just double click to install it). Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us. If you want to uninstall the preference pane when you are done you can just right click on it and there is an option to uninstall.
%center%
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
-> As an alternative you may be able to modify the launch services plist file directly. Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can't locate this file the preference pane mentioned above is the way to go.
-> '''Windows.''' We're looking for a comparable setting on Windows, but reinstalling FileMaker 13 works.
The calendar uses the fmp:/url protocol to call scripts in your file. Some folks computers can get confused as to which copy
-> '''Mac
%center%
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
-> As an alternative you may be able to modify the launch services plist file directly. Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can't locate this file the preference pane mentioned above is the way to go.
-> '''Windows.''' We're looking for a comparable setting on Windows, but reinstalling FileMaker 13 works.
to:
!! Background
The troubleshooting here is for [[administrators]] configuring DayBack. Most of this will be looking at the results of test you can run to examine your config. You'll find this test towards the bottom of the Source Settings screen once you've selected your source:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonlne/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonlne/SettingTests.png]]
The troubleshooting here is for [[administrators]] configuring DayBack. Most of this will be looking at the results of test you can run to examine your config. You'll find this test towards the bottom of the Source Settings screen once you've selected your source:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonlne/SettingTests.png | https://www.seedcode.com/rootimages/stikipad/daybackonlne/SettingTests.png]]
Changed lines 9-47 from:
Note that Event Colors have their own trouble shooting section [[EventColors | 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.
-> '''2.''' Run the "Upon Opening" script again.
-> '''3.''' 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. If you're embedding the calendar, check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''4.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''5.''' 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.
-> '''6.''' 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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''7.''' 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.
-> '''8.''' Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.
-> '''9.''' 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.
!! 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 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.
!! Calendar not loading
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.
to:
My server settings test aren't doing anything
-> If clicking
My server settings test are failing
My server settings test passed but I can't see any events
I can see some events but they're all on the wrong date or for multiple days
-> If clicking
My server settings test are failing
My server settings test passed but I can't see any events
I can see some events but they're all on the wrong date or for multiple days
Changed line 55 from:
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. That causes a problem when DayBack is deployed within a hosted solution. Remove the global storage option on that field to fix the problem.
to:
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.
Changed lines 51-55 from:
--> "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.
to:
--> "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.
!! Calendar not loading
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. That causes a problem when DayBack is deployed within a hosted solution. Remove the global storage option on that field to fix the problem.
!! Calendar not loading
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. That causes a problem when DayBack is deployed within a hosted solution. Remove the global storage option on that field to fix the problem.
Changed line 37 from:
to:
-> '''9.''' 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.
Added lines 36-37:
--> '''9.''' 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.
Changed line 5 from:
-> '''Mac.''' There is a free preference pane you can download that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install [[https://www.rubicode.com/Software/RCDefaultApp/ | this preference pane]]. Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us.
to:
-> '''Mac.''' There is a free preference pane you can download that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install [[https://www.rubicode.com/Software/RCDefaultApp/ | this preference pane]] (once downloaded just double click to install it). Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us. If you want to uninstall the preference pane when you are done you can just right click on it and there is an option to uninstall.
Changed lines 5-6 from:
-> '''Mac.''' There is a preference pane that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install [[https://www.rubicode.com/Software/RCDefaultApp/ | this preference pane]]. Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us.
to:
-> '''Mac.''' There is a free preference pane you can download that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install [[https://www.rubicode.com/Software/RCDefaultApp/ | this preference pane]]. Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us.
Changed line 11 from:
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can locate this file the preference pane mentioned above is the way to go.
to:
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can't locate this file the preference pane mentioned above is the way to go.
Changed lines 7-8 from:
%thumb%[[Attach:rootimages/stikipad/dayback/fmp-url-pref-pane.png | Attach:rootimages/stikipad/dayback/fmp-url-pref-pane.png"URL Protocol Preference Pane"]]
to:
%center%
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
Changed lines 5-10 from:
-> '''Mac.''' There is a preference pane that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp
to:
-> '''Mac.''' There is a preference pane that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install [[https://www.rubicode.com/Software/RCDefaultApp/ | this preference pane]]. Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us.
%thumb%[[Attach:rootimages/stikipad/dayback/fmp-url-pref-pane.png | Attach:rootimages/stikipad/dayback/fmp-url-pref-pane.png"URL Protocol Preference Pane"]]
-> As an alternative you may be able to modify the launch services plist file directly. Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can locate this file the preference pane mentioned above is the way to go.
%thumb%[[Attach:rootimages/stikipad/dayback/fmp-url-pref-pane.png | Attach:rootimages/stikipad/dayback/fmp-url-pref-pane.png"URL Protocol Preference Pane"]]
-> As an alternative you may be able to modify the launch services plist file directly. Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can locate this file the preference pane mentioned above is the way to go.
Changed lines 5-9 from:
to:
[[https://www.rubicode.com/Software/RCDefaultApp/ | link]]
-> '''Mac.''' There is a preference pane that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install this preference pane. Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us.
Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
-> '''Mac.''' There is a preference pane that allows you to select which application is associated with a url protocol. In this case we are referring to the "fmp" protocol. Just download and install this preference pane. Then navigate to the "URL's" tab and find "fmp" in the list of protocols. From there you can choose the proper version of Filemaker you would like to open when that url protocol is invoked. Please note that this preference pane is not made by us, please use at your own risk. We have tested it on Macos X Yosemite and it worked great for us.
Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
Changed line 20 from:
-> '''3.''' Double check the calc fields you added to your events table. 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. If you're embedding the calendar, check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
to:
-> '''3.''' 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. If you're embedding the calendar, check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
Changed lines 30-44 from:
-> '''8.''' Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.
to:
-> '''8.''' Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.
!! 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 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.
!! 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 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.
Changed lines 16-28 from:
-> '''1.''' Run the "Upon Opening" script again.
-> '''2.''' Double check the calc fields you added to your events table. 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. If you're embedding the calendar, check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Dothe timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''4.''' 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.
->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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''6.''' 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.
-> '''7.''' Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.
-> '''2.''' Double check the calc fields you added to your events table. If they begin /* then they're "commented out" and you need to remove the leading /* and trailing */ before
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do
-> '''4
->
-> '''6.''' A few things in
-> '''7.'''
to:
-> '''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.
-> '''2.''' Run the "Upon Opening" script again.
-> '''3.''' Double check the calc fields you added to your events table. 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. If you're embedding the calendar, check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''4.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''5.''' 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.
-> '''6.''' 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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''7.''' 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.
-> '''8.''' Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.
-> '''2.''' Run the "Upon Opening" script again.
-> '''3.''' Double check the calc fields you added to your events table. 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. If you're embedding the calendar, check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''4.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''5.''' 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.
-> '''6.''' 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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''7.''' 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.
-> '''8.''' Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.
Added lines 27-28:
-> '''7.''' Are you filtered and forgot? Click "reset filters" at the bottom of the Filters tab on the calendar's sidebar.
Changed line 1 from:
!! The Calendar Seems to be Opening an Old Copy of FileMaker
to:
!! The Calendar Seems to be Opening an Older Copy of FileMaker
Added lines 25-26:
-> '''6.''' 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.
Changed lines 10-11 from:
!! What's wrong?
to:
!! What's Wrong?
Changed lines 18-45 from:
->''' 3.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches. If you have multiple sources, visit the sources tab and select them one at a time to see if one source is the problem.
-> '''4.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''5.''' Take a look at the calc fields in CalendarRows and make sure nothing has been commented out (commented calcs begin with /* and end with */). You may be able to just remove the comments from the calcs and they'll work. Check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''8.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
!! My startup script keeps deleting and re-creating the calendar interface records, is this normal?
No. But it isn't lethal either. Here is how to fix it.
As you probably know, the calendar requires some dummy records in a table called CalendarRows. Our script " Load Calendar Settings - On Startup --- Edit Configuration Here ---" tries to make sure that users haven't deleted, duplicated, or created new records in this table.
I imagine the reason it is deleting and creating them each time you launch is that the script is no longer running from a layout were it can evaluate "CalendarRows::RowNumber". If you change the beginning of the script to go to a layout based on CalendarInterface (where our home layout is / used to be) the script should only reset the CalendarRows table if there is a problem.
Just don't go to one of the actual calendar layouts just to get to a layout based on CalendarInterface, since those layout are script triggered and could delay / loop your startup.
!! Events are appearing in the wrong place
This is usually caused by carriage returns or other uncommon characters in your data. The most common cause is a trailing carriage return in one of the fields used in your zscEventSummaryCalc field (most likely the Summary or Description field), or ANY carriage return in your Status field (the calendar does not support multiple values in the Status field).
to:
-> '''2.''' Double check the calc fields you added to your events table. 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. If you're embedding the calendar, check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''4.''' 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.
-> '''5.''' 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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''4.''' 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.
-> '''5.''' 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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
Changed line 6 from:
and you'll find an array called LSHandlers and a sub-array LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
to:
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
Changed line 5 from:
-> '''Mac.''' Open ~/Library/Preferences/com.apple.LaunchServices.plist
to:
-> '''Mac.''' Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
Added lines 1-9:
!! The Calendar Seems to be Opening an Old Copy of FileMaker
The calendar uses the fmp:/url protocol to call scripts in your file. Some folks computers can get confused as to which copy of FileMaker to use in responding to these url calls. Fortunately this is pretty easy to fix.
-> '''Mac.''' Open ~/Library/Preferences/com.apple.LaunchServices.plist
and you'll find an array called LSHandlers and a sub-array LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
-> '''Windows.''' We're looking for a comparable setting on Windows, but reinstalling FileMaker 13 works.
The calendar uses the fmp:/url protocol to call scripts in your file. Some folks computers can get confused as to which copy of FileMaker to use in responding to these url calls. Fortunately this is pretty easy to fix.
-> '''Mac.''' Open ~/Library/Preferences/com.apple.LaunchServices.plist
and you'll find an array called LSHandlers and a sub-array LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
-> '''Windows.''' We're looking for a comparable setting on Windows, but reinstalling FileMaker 13 works.
Changed lines 32-36 from:
Just don't go to one of the actual calendar layouts just to get to a layout based on CalendarInterface, since those layout are script triggered and could delay / loop your startup.
to:
Just don't go to one of the actual calendar layouts just to get to a layout based on CalendarInterface, since those layout are script triggered and could delay / loop your startup.
!! Events are appearing in the wrong place
This is usually caused by carriage returns or other uncommon characters in your data. The most common cause is a trailing carriage return in one of the fields used in your zscEventSummaryCalc field (most likely the Summary or Description field), or ANY carriage return in your Status field (the calendar does not support multiple values in the Status field).
!! Events are appearing in the wrong place
This is usually caused by carriage returns or other uncommon characters in your data. The most common cause is a trailing carriage return in one of the fields used in your zscEventSummaryCalc field (most likely the Summary or Description field), or ANY carriage return in your Status field (the calendar does not support multiple values in the Status field).
Changed lines 9-22 from:
->''' 2.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches. If you have multiple sources, visit the sources tab and select them one at a time to see if one source is the problem.
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''4.''' Take a lookat the calc fields in CalendarRows and make sure nothing has been commented out (commented calcs begin with /* and end with */). You may be able to just remove the comments from the calcs and they'll work. Check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
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.
->''6.''' 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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''7.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
-> '''8.''' Make sure you don't have any folders with the same names as your layouts: notably that you don't have a folder named "calendar". Also make sure the name of your file doesnt contain a period in the last 4 characters.
->
-> '''4.''' Take a look
->
-> '''7.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts
-> '''8.''' Make sure you don't have any folders with the same names as your layouts: notably that you don't have a folder named "calendar". Also make sure the name of your file doesn
to:
-> '''2.''' Make sure you don't have any folders with the same names as your layouts: notably that you don't have a folder named "calendar". Also make sure the name of your file doesn't contain a period in the last 4 characters. More on these two issues here: [[YourFile | changes to your file]].
->''' 3.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches. If you have multiple sources, visit the sources tab and select them one at a time to see if one source is the problem.
-> '''4.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''5.''' Take a look at the calc fields in CalendarRows and make sure nothing has been commented out (commented calcs begin with /* and end with */). You may be able to just remove the comments from the calcs and they'll work. Check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''8.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
->''' 3.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches. If you have multiple sources, visit the sources tab and select them one at a time to see if one source is the problem.
-> '''4.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
-> '''5.''' Take a look at the calc fields in CalendarRows and make sure nothing has been commented out (commented calcs begin with /* and end with */). You may be able to just remove the comments from the calcs and they'll work. Check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
-> '''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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
-> '''8.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
Changed lines 21-22 from:
-> '''8.''' Make sure you don't have any folders with the same names as your layouts: notably that you don't have a folder named "calendar".
to:
-> '''8.''' Make sure you don't have any folders with the same names as your layouts: notably that you don't have a folder named "calendar". Also make sure the name of your file doesn't contain a period in the last 4 characters.
Changed lines 29-30 from:
I imagine the reason it is deleting and creating them each time you launch is that the script is no loner running from a layout were it can evaluate "CalendarRows::RowNumber". If you change the beginning of the script to go to a layout based on CalendarInterface (where our home layout is / used to be) the script should only reset the CalendarRows table if there is a problem.
to:
I imagine the reason it is deleting and creating them each time you launch is that the script is no longer running from a layout were it can evaluate "CalendarRows::RowNumber". If you change the beginning of the script to go to a layout based on CalendarInterface (where our home layout is / used to be) the script should only reset the CalendarRows table if there is a problem.
Added lines 22-31:
!! My startup script keeps deleting and re-creating the calendar interface records, is this normal?
No. But it isn't lethal either. Here is how to fix it.
As you probably know, the calendar requires some dummy records in a table called CalendarRows. Our script " Load Calendar Settings - On Startup --- Edit Configuration Here ---" tries to make sure that users haven't deleted, duplicated, or created new records in this table.
I imagine the reason it is deleting and creating them each time you launch is that the script is no loner running from a layout were it can evaluate "CalendarRows::RowNumber". If you change the beginning of the script to go to a layout based on CalendarInterface (where our home layout is / used to be) the script should only reset the CalendarRows table if there is a problem.
Just don't go to one of the actual calendar layouts just to get to a layout based on CalendarInterface, since those layout are script triggered and could delay / loop your startup.
Changed lines 19-21 from:
-> '''7.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
to:
-> '''7.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
-> '''8.''' Make sure you don't have any folders with the same names as your layouts: notably that you don't have a folder named "calendar".
-> '''8.''' Make sure you don't have any folders with the same names as your layouts: notably that you don't have a folder named "calendar".
Changed lines 9-10 from:
->''' 2.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches.
to:
->''' 2.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches. If you have multiple sources, visit the sources tab and select them one at a time to see if one source is the problem.
Changed lines 11-12 from:
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown?
to:
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown? Do the timestamp fields show the same date / time as the date / time fields? (If not, skip to no 6 below.)
Changed lines 17-18 from:
-> '''6.''' 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.)
to:
-> '''6.''' 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 [[MultipleSources | more than one source]]; if the sources are using different date and time fields they'll need different timestamp calcs.
Changed lines 17-19 from:
-> '''6.''' 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.)
to:
-> '''6.''' 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.)
-> '''7.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
-> '''7.''' If you're having display issues, make sure the calendar layouts only have a body part; there should be no header or footer parts on the 4 main calendar layouts.
Changed lines 15-17 from:
-> '''5.''' 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.
to:
-> '''5.''' 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.
-> '''6.''' 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.)
-> '''6.''' 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.)
Changed lines 13-14 from:
-> '''4.''' Take a look at the calc fields in CalendarRows and make sure nothing has been commented out (commented calcs begin with /* and end with */). You may be able to just remove the comments from the calcs and they'll work.
to:
-> '''4.''' Take a look at the calc fields in CalendarRows and make sure nothing has been commented out (commented calcs begin with /* and end with */). You may be able to just remove the comments from the calcs and they'll work. Check the auto enter calc definitions as well, such as those for DateRangeStartAutoGlob and DateRangeEndAutoGlob.
Changed lines 13-15 from:
-> '''4.''' 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.
to:
-> '''4.''' Take a look at the calc fields in CalendarRows and make sure nothing has been commented out (commented calcs begin with /* and end with */). You may be able to just remove the comments from the calcs and they'll work.
-> '''5.''' 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.
-> '''5.''' 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.
Changed lines 7-13 from:
-> 1. Run the "Upon Opening" script again.
-> 2. Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches.
-> 3. Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown?
-> 4. 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.
-> 2. Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches.
-> 3. Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown?
-> 4. 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.
to:
-> '''1.''' Run the "Upon Opening" script again.
->''' 2.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches.
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown?
-> '''4.''' 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.
->''' 2.''' Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches.
-> '''3.''' Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown?
-> '''4.''' 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.
Added lines 1-13:
!! What's wrong?
If you can't see any events in the calendar after your integration, here are a couple things to check.
Note that Event Colors have their own trouble shooting section [[EventColors | here]].
-> 1. Run the "Upon Opening" script again.
-> 2. Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches.
-> 3. Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown?
-> 4. 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.
If you can't see any events in the calendar after your integration, here are a couple things to check.
Note that Event Colors have their own trouble shooting section [[EventColors | here]].
-> 1. Run the "Upon Opening" script again.
-> 2. Click on the filters tab: if "Clear" is showing up in red, click "clear" to empty the filters. You may have been "searching" for events that don't have any matches.
-> 3. Check out the Source No 1 layout in browse mode, reviewing every tab: are there any errors shown?
-> 4. 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.
