SCSubscribe

Field Mapping

SCSubscribe.FieldMapping History

Hide minor edits - Show changes to output

July 30, 2013, at 11:07 PM by 67.190.87.90 -
Changed line 1 from:
Select the fields in your FileMaker database that represent the corresponding fields in the iCal data format. Title, timestamp start and timestamp end are required, so if you don't have these fields in your database, you'll need to add them. If you have FileMaker Advanced, you can copy/paste the "TimestampStartCalc" and "TimestampEndCalc" fields from the included "AppointmentsExample.fmp12" file.
to:
Select the fields in your FileMaker database that represent the corresponding fields in the iCal data format. Title, timestamp start and timestamp end are required, so if you don't have these fields in your database, you'll need to add them. Note that the starting and ending timestamp fields need to actually be of the data type "Timestamp". If your database just has date and time fields (that would not be uncommon), look at the "TimestampStartCalc" and "TimestampEndCalc" fields in the included "AppointmentsExample.fmp12" file to see how we've calculated timestamp values from date and time fields. Feel free to copy/paste these fields into your own file.
July 29, 2013, at 01:53 PM by 50.132.84.245 -
Changed lines 13-15 from:
-> Your event must have a start date. If the start date is empty, SeedCode Subscribe will throw an error.
-> You can leave the end date blank.
->
If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
to:
-> Your event must have a start date: if the start date is empty SeedCode Subscribe will throw an error. So if some of your events have blank start dates you'll need to account for that in your [[filter criteria | filters]] so only events with start dates are in the calendar.

-> You can leave the end date blank but you must map to an end date field,


-> If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
July 29, 2013, at 01:52 PM by 50.132.84.245 -
Changed line 9 from:
Read about special field-naming considerations for [[Google | Google Calendar]].
to:
Read about special field-naming considerations for [[Google Calendar]].
July 08, 2013, at 06:34 PM by 67.190.87.90 -
Changed lines 1-2 from:
Select the fields in your FileMaker database that represent the corresponding fields in the iCal data format. Title, timestamp start and timestamp end are required, so if you don't have these fields in your database, you'll need to add them.
to:
Select the fields in your FileMaker database that represent the corresponding fields in the iCal data format. Title, timestamp start and timestamp end are required, so if you don't have these fields in your database, you'll need to add them. If you have FileMaker Advanced, you can copy/paste the "TimestampStartCalc" and "TimestampEndCalc" fields from the included "AppointmentsExample.fmp12" file.
June 27, 2013, at 12:11 AM by 67.190.87.90 -
Changed lines 13-14 from:
-> Your event must have a start date.
-> If the start date is empty, SeedCode Subscribe will throw an error.
to:
-> Your event must have a start date. If the start date is empty, SeedCode Subscribe will throw an error.
June 14, 2013, at 06:32 PM by 67.190.87.90 -
Changed lines 13-16 from:
Your event must have a start date.
If the start date is empty, SeedCode Subscribe will throw an error.
You can leave the end date blank.
If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
to:
-> Your event must have a start date.
-> If the start date is empty, SeedCode Subscribe will throw an error.
-> You can leave the end date blank.
-> If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
June 14, 2013, at 06:31 PM by 67.190.87.90 -
Changed lines 13-16 from:
* Your event must have a start date.
* If the start date is empty, SeedCode Subscribe will throw an error.
* You can leave the end date blank.
* If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
to:
Your event must have a start date.
If the start date is empty, SeedCode Subscribe will throw an error.
You can leave the end date blank.
If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
June 14, 2013, at 06:31 PM by 67.190.87.90 -
Changed line 13 from:
* Your event must have a start date.
to:
*  Your event must have a start date.
June 14, 2013, at 06:29 PM by 67.190.87.90 -
Changed lines 14-16 from:
->If the start date is empty, SeedCode Subscribe will throw an error.
->*You can leave the end date blank.
->If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
to:
* If the start date is empty, SeedCode Subscribe will throw an error.
* You can leave the end date blank.
* If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
June 14, 2013, at 06:28 PM by 67.190.87.90 -
Changed line 13 from:
->*Your event must have a start date.
to:
* Your event must have a start date.
June 14, 2013, at 06:27 PM by 67.190.87.90 -
Changed line 13 from:
*->Your event must have a start date.
to:
->*Your event must have a start date.
Changed line 15 from:
->You can leave the end date blank.
to:
->*You can leave the end date blank.
June 14, 2013, at 06:27 PM by 67.190.87.90 -
Changed line 13 from:
->Your event must have a start date.
to:
*->Your event must have a start date.
June 14, 2013, at 06:25 PM by 67.190.87.90 -
Changed lines 13-16 from:
Your event must have a start date. If the start date is empty, SeedCode Subscribe will throw an error. You can leave the end date blank. If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
to:
->Your event must have a start date.
->If the start date is empty, SeedCode Subscribe will throw an error.
->You can leave the end date blank.
->If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date.
June 14, 2013, at 04:11 AM by 67.190.87.90 -
Changed lines 9-13 from:
Read about special field-naming considerations for [[Google | Google Calendar]].
to:
Read about special field-naming considerations for [[Google | Google Calendar]].

!!About your date fields...

Your event must have a start date. If the start date is empty, SeedCode Subscribe will throw an error. You can leave the end date blank. If an event's end date is before its start date, SeedCode Subscribe will change the end date to match the start date
.
June 12, 2013, at 10:04 PM by 67.190.87.90 -
Changed lines 7-9 from:
Yes! Just put the related fields you want to be able to choose from on your SeedCode Subscribe layout. You can filter on related fields, too.
to:
Yes! Just put the related fields you want to be able to choose from on your SeedCode Subscribe layout. You can filter on related fields, too.

Read about special field-naming considerations for [[Google | Google Calendar]]
.
June 11, 2013, at 08:26 AM by 67.190.87.90 -
Changed lines 3-7 from:
Description, time zone, color, location and URL are optional fields.
to:
Description, time zone, color, location and URL are optional fields.

!! Can I use related fields?

Yes! Just put the related fields you want to be able to choose from on your SeedCode Subscribe layout. You can filter on related fields, too
.
June 06, 2013, at 03:22 AM by 67.190.87.90 -
Added lines 1-3:
Select the fields in your FileMaker database that represent the corresponding fields in the iCal data format. Title, timestamp start and timestamp end are required, so if you don't have these fields in your database, you'll need to add them.

Description, time zone, color, location and URL are optional fields.
(855) SEEDCODE
support@seedcode.com
Follow us: