SENT – Send HTML Email From FileMaker Pro

Edinburgh, Scotland – July 11, 2019 – WhiteSpace Systems Ltd., a leader in producing high quality, efficient FileMaker® solutions, is proud to announce the launch of our eagerly awaited SENT app.

This FileMaker app allows you to send HTML emails directly from a FileMaker Pro Webviewer.

SENT has the following features:

  • Send HTML Emails.
  • Include attachments from either a Container field or directly from your filesystem.
  • Native FileMaker, no 3rd party plugins.
  • Simple to set up. Only a few custom functions and a Webviewer are required.
  • Unlimited discreet automatic updates.
  • Backwards compatible to FileMaker 14.

As a company and since FileMaker 8.5 introduced the Webviewer object, we have looked to develop a WYSIWYG (What you see is what you get) for rich text editing. Most of our solutions have the ability to send HTML email from within FileMaker Pro. We would always end up purchasing a plugin to accomplish this. It would worked fine but it always consisted in us having to build an email client in FileMaker and then the scripts to handle the sending of the email. This grew tiresome and we wished for a quicker solution to send HTML Email directly from FileMaker Pro.

Our main goal with SENT was to take away the complexity of sending html emails with attachments in FileMaker. This would make it accessible for novice to intermediate FileMaker developers. Even experienced developers will find SENT useful as it takes away all the complexity of SMTP and reduces it to just a few custom functions.

Steven McGill, Director, WhiteSpace Systems Ltd.

SENT has a free limited demo mode. This allows you to quickly test email sending and make evaluate if SENT is the right solution for solving your problem of sending HTML emails from FileMaker Pro.

For more information on SENT, visit

For documentation of SENT, visit

FileMaker Data API and Portal Filters

We’re currently working on a project where we are exposing the FileMaker Data API to some web technologies. The team working on the Web side of things have asked for the portal data passed back by the Data API to be filtered between a date range.

To do this with a relationship would mean having the current date in every parent record and we’d need to update this daily. Not the smartest way but it would work.

However we wondered if portal filters would work and sure enough the JSON passed back by the Data API was filtered based on the portal filter we placed on the layout.

tldr; You can use portal filters on a FileMaker layout and this will translate over to the FileMaker Data API response.

We also discovered that if you give your portal an object name, this too will be reflected in the Data API response object

 "response": {
  "data": [
    "fieldData": {...},
    "portalData": {
     portalLayoutObjectName: [...],
 "messages": {...}
 "fieldData": "...",


A CSV Parser that converts CSV into JSON on the FileMaker Pro Platform.

I was browsing over at the FileMaker forums and came across a question about parsing CSV data.

This caught our interest and made us ask the question.

Could we take some CSV data and transform it into a valid JSON Object?

The answer was yes and with that we present fm-csv2json.

A FileMaker script which when passed a valid CSV string, will covert this string into a JSON object.

Download free over on Github.

We also have a similar parser that turns XML into JSON too.


FileMaker Web Direct Clock

I was browsing over at /r/filemaker/ and came across the following thread.

I’ve got a running clock javascript that works when opening from Filemaker, but can’t run correctly on webdirect because of the GetDate() function. I was wondering if anyone had a solution to pulling the date from the server so the clock will be uniform everywhere.


After spending about an hour or so playing around, to see if we could actually build a running Filemaker Web Direct clock. We produced the following solution:

Let (
    _ts = 
      ( GetAsNumber ( Get ( CurrentHostTimestamp ) ) 
      - GetAsNumber ( Timestamp ( "1/1/1970" ; "00:00:00" ) ) 
      + Floor ( Get ( CurrentTimeUTCMilliseconds ) / 1000 ) 
      - GetAsNumber ( Get ( CurrentTimestamp ) ) ) * 1000 ;
    _html = 
      <!DOCTYPE html>
              function startTime(today) {
                var start = new Date(" & _ts & ");
                  /* delta is used to reduce time slippage */
                  var delta = new Date() - start;
                  if(today) {
                    var today = new Date(
                      today.getMilliseconds() + delta
                  } else {
                    var today = new Date(
                      start.getMilliseconds() + delta
                  var h = today.getHours();
                  var m = today.getMinutes();
                  var s = today.getSeconds();
                  m = checkTime(m);
                  s = checkTime(s);
                  document.getElementById('txt').innerHTML =
                  h + ':' + m + ':' + s;
                }, 100);
              function checkTime(i) {
                if (i < 10) {i = '0' + i};
                return i;
          <body onload='startTime()'>
            <div id='txt'></div>
        " ;
    _result = 
      Case (
        PatternCount ( Get ( ApplicationVersion ) ; "Web" ) ;
          "data:text/html;base64," & Base64Encode ( _html ) ;
        "data:text/html," & _html
  ] ;


Paste the above code into any web viewer and it will produce the following FileMaker Web Direct Clock!

Filemaker Web Direct Clock

The script makes use of Get ( CurrentHostTimestamp ). This keeps any client, whether using web direct or FileMaker Pro, in sync as the time source is consistent between clients.

The _ts variable is used to convert a FileMaker Timestamp into an Epoch timestamp required in Javascript.

The javascript var delta is required because the javascript function setInterval(...) is not guaranteed to consistently run at the ms value you give it. This variable allows for the slippage to be calculated and be added or subtracted to the time to keep it in sync. We initially didn’t have this and noticed that within 5 minutes our web direct clock and our system clock where out of sync by a matter of minutes.


Get ( CurrentHostTimestamp ):

FileMaker Epoch Method:

Javascript Clock:

Javascript timer slippage: