Christos Savva, Fabio Bosisio and Vince Menanno from Beezwax present at dotfmp Berlin, 2023.
This week we’re in Berlin… one of the stops on the Road to Claris Engage 2024 …gathering with the developer community, and highlighting innovation for the Claris FileMaker platform development. As conference speakers at dotfmp Berlin (June 1-3), Christos Savva, Fabio Bosisio and Vince Menanno from Beezwax present three sessions:
Enhancing FileMaker with Python
What do you do with all this historical data in your app? [AWS Athena Interactive SQL / Serverless / S3 with FileMaker]
Elements for Building Great Solutions [FileMaker UX & DX]
FileMaker 2023 introduces Perform Script on Server with Callback, a new asynchronous method to execute scripts with FileMaker Server. Now we have a way for FileMaker Server to execute another script, a “Callback” script, when one script is done processing via Perform Script on Server. It’s like calling your virtual assistant and instead of waiting on the phone for 5 minutes for info, they basically call you back when they are ready with an answer.
The end result is improved performance, better management of complex script workflow, enhanced user experience, and new possibilities for handling integration with APIs, email and services like Claris Connect.
Five Ways InspectorPro 7 Can Improve Your FileMaker Code
Want better collaboration, performance and insight for your FileMaker development teams? With InspectorPro you can leverage advanced diagnostics, perform in-depth analysis, and gain insights with new visualizations.
Check out these videos from InspectorPro creator & Beezwax Chief Innovation Officer, Vince Menanno.
Problem Reports Dashboard
Track your progress while reducing problem code, and reducing technical debt.
Script transactions in Claris FileMaker are finally here, but wait! Haven’t we done “transactions” in FileMaker for a long time? Yes and Yes. But script transactions are different and the main advantages, that I see, are the possibilities of simplifying code and improving solution performance. I’ll elaborate on these in this post. And, of course, there is also the inherent benefit of doing things transactionally … all or nothing is the law of the data.
I often like to measure performance, because I am curious if some small change can lead to subtle, or maybe not so subtle, improvements. For the longest time my Swiss Army knife for measuring Claris® FileMaker® performance has been:
Vincenzo Menanno and Fabio Bosisio from Beezwax present at Rome FileMaker Week.
This week we’re in Italy… formazione, condivisione e ancora divertimento [training, sharing and more fun] …with the focus on innovations in Claris® FileMaker platform development. As realtori [conference speakers] at Rome FileMaker Week (October 6-8), Vince Menanno and Fabio Bosisio from Beezwax present three sessions:
Local FileMaker Development with Docker and Node-RED
The New Horizon: Native Script Transactions in FileMaker
La 7e Conférence québécoise des développeurs FileMaker (CQDF) 2022: les 15 et 16 Septembre 2022 à l’Auberge Saint-Gabriel, Montreal. Vincenzo Menanno, Beezwax, présente “Le nouvel horizon | Transactions de script natif” avec Claris (FileMaker) Pro.
As Claris gets further into an Agile groove, there are product releases more often, always with new features and improvements. Claris FileMaker 19.5 is no exception. It includes many new features, expanded extensibility, performance enhancements, and reliability improvements. I want to bring attention to one simple thing that promises to change the world for many of us in the FileMaker developer community: Save a Copy as XML…and the performance improvements running this on FileMaker Server.
Building a custom Tableau® Connector for Claris® FileMaker® enables faster, more reliable and more flexible connections between Tableau and FileMaker datasources, compared with the legacy Web Data Connector.
For a number of Beezwax client projects, we’ve installed and deployed a Tableau Connector (aka “TACO”) for FileMaker. The TACO was built using the Tableau Connector SDK (provided by Tableau) to connect to datasources on FileMaker Server. The TACO method uses JDBC rather than the FileMaker Data API for the connection between FileMaker and Tableau, and in our testing the performance of data extracts was up to 10 times faster.
Let’s talk about Claris® FileMaker® and transactions! Vincenzo Menanno discusses what transactions are, how they relate to FileMaker data operations (creating, updating, and deleting records), database normalization, and how to use transactional concepts to improve FileMaker performance, especially over a wide area network (WAN).
When the Apple silicon Macs with M1 chips came out, I read and watched many of the reviews. Most of them had great things to say about the promise of Apple’s new M1 chip…I was impressed. When I finally received my Apple M1 MacBook Pro, and started to use it…I was amazed.
Back in 2020, FileMaker Pro 19.2 wasn’t optimized yet for Apple silicon processors, but ran fine under Rosetta emulation. On my M1 MacBook Pro, it already felt much faster than running FileMaker “natively” on an Intel-based MacBook…I was astonished.
Today, I’m running the just-released Claris FileMaker® 19.3, with native support for Apple’s M1 chip, on a new MacBook Pro. It is, in a word: Astounding!
Everything about the M1 Apple silicon leaves you simply delighted and surprised. It’s like the first time you drive a super-charged Tesla and feel the rush of powerful acceleration OR I imagine it’s like when Han Solo first blasts the Falcon into light speed: it must be experienced to be believed.
Combining functions, features, or steps in creative new ways can deliver productive results. I was thrilled to discover in FileMaker 18 that the new file-based script steps give us the ability to perform imports natively on FileMaker Server, with no configuration or changes needed.
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?”→
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”→
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”.
A few years ago, I worked on a FileMaker project where the client told us that every week they need to import about 7,000 rows of data that represent some information that this company uses. And every week there might be some modified records, some records that don’t show up any longer, and some new records that hadn’t already existed. For this example, let’s just call it this data “Products”.