By Craig Saunders and Oscar Frith-Macdonald, 28 August 2024
Let’s face it, the tech world is going crazy over “AI” with promises of exciting and seemingly unlimited potential on offer. There’s a lot of hype, and it’s hard to determine the reality of what ’ve got now, where it’s going, and what we can and should be doing with it all.
So our aim here is to “keep it real” and take a close and practical look at the ways we can use AI tools now to enhance FileMaker solutions. Our plan is to keep experimenting with the new stuff and to share here in our blog what we’re learning and what we’re thinking can be achieved.
As an example, the new Semantic Search capabilities mean we can provide the ability to search textual data stored in the database based on “meaning”. The implications of that are that maybe we could be capturing and storing more descriptive text in our solutions.
To begin with, Oscar's written a great foundational piece looking at the way AI technologies are built. If you’re a developer, it really helps to have that stuff in mind, so we recommend starting there:
Semantic Search
Our first "deep dive" is into semantic search with FileMaker:
But as part of this intro, let’s first take stock…
The standard API capabilities already in FileMaker have allowed us to integrate external AI services but there are now new features coming to FileMaker which open doors for how we use AI right within the database. FileMaker also has had the ability to use machine learning (great for pattern recognition) for a long time.
But as of latest version of FileMaker 2024, we’re seeing the first specific tools for LLM and generative AI being added to the platform — Claris are rolling these new features out progressively with each new update. Here’s what the state of play is now:
New AI script steps:
New AI functions:
As you can see from this list, FileMaker is currently geared towards embedding vectorized LLM data and using that to perform semantic searches, so that’s what we’ll start with.
Before you dive in, here are a few considerations to keep in mind:
A general rule of thumb: Don't use AI to modify actual data in your systems.
As discussed in our previous article, it’s crucial not to allow AI to directly modify your FileMaker data due to the potential pitfalls. For instance, you should avoid letting an AI model calculate your average invoice amount or handle anything related to numerical data—tasks better suited to traditional tools in FileMaker. Remember, the AI models we’re working with are large language models, not mathematical models.
Instead, use AI to provide recommendations and insights, which you can then review and implement manually. AI can also be a great tool for summarising large blocks of text, though you may want to add an extra line at the end to state that this summary was produced by an AI model, similar to OpenAI’s DALL_E 3 adding an AI watermark in the metadata.
This approach ensures:
If you are going to allow an AI to modify your data, it is important to keep an unmodified version of that data and have a human verify any modifications the AI makes.
Now with the warning out of the way, what are some good uses of AI in your FileMaker solution?
AI can quickly analyse large datasets to identify patterns, trends, and anomalies that might not be immediately obvious to a user.
By using historical data, AI can make predictions about future outcomes. In FileMaker, predictive analytics can be applied to:
AI can improve the search capabilities of your FileMaker databases by understanding context and relevance, leading to more accurate and relevant results. In FileMaker, enhanced search functionalities can:
AI-powered natural language interfaces enable users to interact with FileMaker using everyday language. In FileMaker, natural language capabilities can:
While we did mention that AI can be used for data analysis, reporting, and predictive analytics, These are tasks more suited to the machine learning side of AI, and these tools have already existed in FileMaker for a long time.
As previously mentioned, the new script steps introduced with FileMaker 2024 are geared towards embedding (or vectorizing) your data through a language model (LLM) and using that approach to perform semantic searches on it. So let’s dive into adding a semantic search to a FileMaker solution:
Something to say? Post a comment...
Comments
No one has commented on this page yet.
RSS feed for comments on this page | RSS feed for all comments