Your File
ProMaps.YourFile History
Hide minor edits - Show changes to output
Changed lines 1-8 from:
!! Do I need to do anything special to get my file ready for SeedCode Calendar?
Not really. You'll be pasting thecalendar into your file, and importing a number of scripts, but that is all described in our [[integration]] article.
There are, however, a couple things to keep in mind about your file: things that could stop thecalendar from working properly if not addressed.
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyCompany.com.fp7 is not).
Not really. You'll be pasting the
There are, however, a couple things to keep in mind about your file: things that could stop the
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyCompany.com.fp7 is not).
to:
!! Do I need to do anything special to get my file ready for SeedCode ProMaps?
Not really. You'll be pasting the map into your file, and importing a number of scripts, but that is all described in our integration article.
There are, however, a couple things to keep in mind about your file: things that could stop the map from working properly if not addressed.
Not really. You'll be pasting the map into your file, and importing a number of scripts, but that is all described in our integration article.
There are, however, a couple things to keep in mind about your file: things that could stop the map from working properly if not addressed.
Added lines 1-11:
!! Do I need to do anything special to get my file ready for SeedCode Calendar?
Not really. You'll be pasting the calendar into your file, and importing a number of scripts, but that is all described in our [[integration]] article.
There are, however, a couple things to keep in mind about your file: things that could stop the calendar from working properly if not addressed.
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyCompany.com.fp7 is not).
'''Privilege Sets.''' If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding three new tables when you integrate the calendar and your users will need to be able to add, edit, and delete records in all three (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
-> You'll also want to make sure that the layouts you create are accessible to each of your privilege sets: check the same thing for value lists and scripts.
Not really. You'll be pasting the calendar into your file, and importing a number of scripts, but that is all described in our [[integration]] article.
There are, however, a couple things to keep in mind about your file: things that could stop the calendar from working properly if not addressed.
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyCompany.com.fp7 is not).
'''Privilege Sets.''' If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding three new tables when you integrate the calendar and your users will need to be able to add, edit, and delete records in all three (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
-> You'll also want to make sure that the layouts you create are accessible to each of your privilege sets: check the same thing for value lists and scripts.
