Troubleshooting
SeedCodeComplete2.Troubleshooting History
Hide minor edits - Show changes to output
Changed lines 19-25 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.
!! Script debugging tips
Needless to say we find the script debugger in FileMaker Advanced pretty indispensable when we're tracking things down. If you do too, then this should help:
Some of the scripts in Complete step into our license file so we can enforce our license. It's actually pretty easy to skip this in the debugger once you know how. This video walks you through it: http://www.youtube.com/watch?v=aEfumAM_IyU
!! Script debugging tips
Needless to say we find the script debugger in FileMaker Advanced pretty indispensable when we're tracking things down. If you do too, then this should help:
Some of the scripts in Complete step into our license file so we can enforce our license. It's actually pretty easy to skip this in the debugger once you know how. This video walks you through it: http://www.youtube.com/watch?v=aEfumAM_IyU
Changed lines 3-4 from:
If you've added [[Multiple Souces | sources]] to the calendar, or changed the mapping on our Source No 1 layout, and you're not seeing what you expect in the calendar, here are a couple things to check.
to:
If you've added [[Multiple Sources | sources]] to the calendar, or changed the mapping on our Source No 1 layout, and you're not seeing what you expect in the calendar, here are a couple things to check.
Changed lines 3-4 from:
If you can't see any events in the calendar after your integration, here are a couple things to check.
to:
If you've added [[Multiple Souces | sources]] to the calendar, or changed the mapping on our Source No 1 layout, and you're not seeing what you expect in the calendar, here are a couple things to check.
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.
