Jump to content
  • entries
    494
  • comments
    6
  • views
    32,102

Sending Email with Merge Fields


FileMaker Magazine

629 views

No Access? Watch the preview video here. video-x-generic.pngSendingEmailMerging_Pre.mp4
Attachment Size
package-x-generic.pngSendingEmailMergeFields.zip 388.62 KB
By Matt Petrowsky

What would a database solution be without the ability to send email? Well, it would be a database solution without the ability to send email - but who wants that right?

Email is obviously an integral part of our modern day communication. And, despite what the Twitters, Facebooks and Instagrams of the world would have you believe, email is here to stay.

The easiest way to add email support to a FileMaker database is to simply use the Send Mail script step. But, that’s boring, and sometimes it doesn’t work. Especially when you’re using an email client not supported by FileMaker. The Send Mail step alone also has limited use when, most of the time, the intended objective is to integrate data from the database.

Therefore, we need to integrate the data from our fields. The easiest way to do this is to use FileMaker’s <<mergeFields>> right within the content of a text block somewhere on the layout, or off to the side of the layout, and then using the function GetLayoutObjectAttribute ( “My_Merge_Email” ; "content" ).

The problem we hit is that this is not user friendly. You don’t often give users the ability to edit layouts. So why not emulate the way FileMaker works with merge fields and simply do the same thing using data which is stored within fields?

This video showcases one of the most streamlined and easy-to-implement solutions for handling merge values into content stored within a field. Using the content provided here you’ll have an email merging and sending solution within mere minutes every time you need it!

Tags: 


View the full article

0 Comments


Recommended Comments

There are no comments to display.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.