Professional Documents
Culture Documents
Quick Start Guide
Quick Start Guide
5. Click “Merge” in the lower right and your found set of contacts will be merged
with this mailing, creating the letters you can now print using the “Print Letters”
button in the lower right of the screen.
6. Close the window when you’re done printing. That’s it; you’ve just merged your
first mailing.
For fmSpark to work correctly, it must be 'stitched' to your solution using the
relationship graph in fmSpark.fp7.
fmSpark ships with an example Contacts database that is already attached to it,
but the quickest way to get fmSpark working with your solution is to repoint the
table occurrence away from the example database and point it at your own
contacts database.
More detailed instructions for all this can be found in fmSpark’s built in
documentation: just click the “Help” button in the upper right of most screens.
1. Double click on fmSpark.fp7: the plugins were probably installed for you
automatically, but you may need to close and re-open FileMaker for them to
become active.
2. Click the Settings button the top right corner of the Welcome screen and fill
in your user and email server information.
In fmSpark.fp7, select Manage Database > External Data Sources from the
File menu. (In FileMaker 8.5 this would be Define > File References...)
1. Re-point the CONTACTS data source to your database file containing contact
records (names, email addresses, etc).
2. Next, go to the Relationship Graph and double click on the CONTACTS table
occurrence, pointing it at the contacts table in your file. Make sure you keep
Since your contacts table likely has different fields and field names than
fmSpark’s sample file, the merge fields and templates in fmSpark won’t line up
with your fields.
From the fmSpark menu select “Settings” and then click the “Developer” icon in
the upper right of the screen. Select the “Fields and Functions” tab and then,
making sure that the “CONTACTS” is selected in the “Table” filter in the upper
left, click the “Rebuild” button.
This will add all of your fields as possible merge fields in fmSpark. Down the
road you can search the built in documentation for “Merge Fields” to find out
how to exclude fields from this list, but this quick rebuild will get you going.
Note: The templates that come with fmSpark also use the field names from the
sample Contacts file. You’ll likely need to modify these after rebuilding
fmSpark with your field names.
You will need to modify the “Manage Recipients (Contact)” layout if you want to
be able to deselect recipients from within fmSpark. There are five simple steps
involved:
1. From the Welcome screen enter Layout Mode and switch to the “Manage
Recipients (Contacts)” layout
2. Select the field now reading <<Field Missing>> and choose Field/
Control... > Setup from the Format menu. Select the appropriate name
field from the list of fields in your solution. This is likely your contact’s
name.
3. Select the field and choose Button Setup... from the Format menu. Click
the “Specify” button and ensure the Script Parameter at the bottom is the
primary key you selected in Step 3 above.
4. Next, select the field and choose Conditional... from the Format menu.
Ensure the contact ID field in the “Condition” is the primary key you
selected in Step 3 above. So the calc might now read: not MemberOf
( _Merge Batch::entityIDs ; _CONTACTS Recipients::My Contact ID)
5. Double-click on the portal to bring up the Portal Setup dialog. Click on
“Specify” to change the Sort Order for the portal to one using your fields.
The easiest way to get started here is to go to the SampleContacts.fp7 file and
copy the four example scripts from SampleContact.fp7 into your own contacts
database. Add the following scripts:
o Open fmSpark
o Create Letters Foundset
o Create Emails Foundset
o Create Labels Foundset
You'll need to make a small change to each of the “Create...” scripts you just
added to your file. Edit the script "Create Letters Foundset" and you'll see a
comment “NOTE: change to use your primary key (ID) in the following line”
shown below:
Edit the Set Variable following “NOTE” and remove the comments (the /* at the
beginning of the calculation and the */ at the end). Then replace
Contacts::Contact ID with the field which is the primary ID in your table: the
same primary key you used in step 3 above.
Remember, you'll make this same change in each of the “Create...” scripts you
brought in from Sample Contacts.
From the fmSpark menu, select “Settings...” and then click the Developer button
in the upper right, the second portal you see on the Media and Groups tab is
called “Merge Groups.” There are two settings here where you’ll need to enter
the name of the field you use for your contact’s full name:
Remember that you kept the table occurrence names (things like “_CONTACTS
Recepients”) the same in step 3 above, so you just need to change the text to
the right of the “::”. Be sure to change both field names above, leaving the table
occurrence name alone.