Once you have crafted a Tableau dashboard, pulling data from your FileMaker solution, then your next goal might be to make sure the dashboard data gets refreshed at regular intervals, and in an efficient manner. And that is what we’ll do in this blog post.
Now that the FileMaker Data API has been officially released (with FileMaker 17), it is time to share an update on Tableau-to-FileMaker integration. I originally wrote about integrating Tableau and FileMaker to create a match made in data heaven. I’ll also be speaking on “FileMaker + Tableau” at FileMaker DevCon 2018.
I’m always excited each time the FileMaker Platform gets new capabilities. It isn’t just the new features on their own that make things interesting, but what happens to the platform as a whole which provides for some interesting and inspiring innovations. In this case, it is a new way to do transactional record editing in FileMaker. This is the first in a multi-part series on this topic.
Continue reading “How Transactional is the FileMaker Data API?”
One of the most exciting new features of FileMaker 17 isn’t part of the product, technically: it’s a command line function called the Data Migration Tool. You invoke it from the terminal, but don’t let that fool you. This is a uniquely powerful tool, one that honors the pitfalls of developing in a hosted, high-trafficked app — finally.
The Data Migration Tool allows you to merge two files, so you can develop in an offline copy and then migrate the live system into your improved app. Migration includes user accounts, value lists, serial numbers and of course data, all at once.
Continue reading “FileMaker Data Migration Tool – New Ways To Code In Complex Environments”
In looking back at our initial approach to logging FileMaker PSoS (Perform Script on Server) activity, I reflect back on a number of times where this has been extremely helpful. If you have come to rely on the benefits of PSoS then you also know some of its challenges — one of the biggest is debugging and monitoring how long sessions take.
Since FileMaker 16 introduced JSON, in new systems we’ve switched over to using JSON as the main way of exchanging data for parameters. Because we also use PSoS in new systems, we updated our method for PSoS Logging and this blog entry talks about the changes we made there and also restates the usefulness of this log.
Continue reading “Logging PSoS Activity: Episode III – Return of the JSON”
Last year when I wrote this blog post we were talking about FileMaker 16 and the Data API being in beta. Now that FileMaker 17 has officially been released and along with it the Data API is out of beta and is a version 1.0.
Highlighting insight, performance and collaboration
Wow! InspectorPro 6 is finally here. Can’t even believe it. It was such a massive undertaking. Lots of great new things and many improvements. Really proud of this release. In the immortal words of the late Steve Jobs… “This is our best version ever”.
The Lesson of Context
One of the first lessons I learned with FileMaker is that of context! Layouts, reports, calculations, scripts, and so on all act from the perspective of a single Table Occurrence (TO) — the “context” — pulling in data from related tables as needed.
Generally, the record set being acted on is the set of records in that context table occurrence or a found subset thereof. There are a few exceptions to this, however, and today we’re going to explore one of those.