Using an abstract approach to development makes possible to drastically reduce the amount of scripts, formats, fields in use, making your solutions much faster. It proportionally decreases the time needed for development, maintenance and debugging.
In this session we will see how some simple basic tricks in the setup phase and an abstract approach can drastically change the quality of your development: you can also create a series of modules to freely use in all your projects.
Giancarlo Meak & Marco Viele
What are the processes that need to be digitized according to the legislation?
How does this affect the life of the FileMaker developer?
How to send commands to the cash register?
In this session we will see how the electronic receipt problem – mandatory since 1 July 2019 – has been brilliantly solved, starting from what the law provides in a real and practical example of integrating a fiscal recorder into a FileMaker flow.
Machine learning is a disruptive technology that is affecting all industries. The fuel for machine learning is data. This session will discuss how FileMaker data can be harnessed by machine learning in order to impact your own or your client’s bottom line. Learn more about what machine learning is, the financial impacts on business, integration with FileMaker, and various types of machine learning tools and services. Find out how to implement some simple FileMaker and machine learning examples.
Bug Off! Don’t let the bugs in!
Let’s find out with Mr Watson how to disinfect our solutions, eliminating problems and “bugs”!
What are the tools that FileMaker makes available to us to find errors? How to best use them?
Armed with the latest tools from the fmWorkMate toolbox, we will find and exterminate a lot of bugs and learn how to keep them at bay every day.
The best way to resolve an infestation is to not let insects enter; and with mistakes it’s the same thing!
Working in FileMaker, we are used to easily and even complex operations: the specific structure of FileMaker makes development really easy. However, when we need to interface FileMaker with something else, the problem lies precisely in the word “specific”: standards are needed to allow connection to our database of external systems.
Data APIs are born with this purpose: to open FileMaker to the rest of the world, using standard protocols like REST, OAUTH, POST and GET. In this way it is possible to allow other Web Apps and Services to interact directly with our FileMaker Application, or even use an app (FileMaker or not) without the need for a continuous connection to FileMaker Server.
In this session we will start from scratch, discovering the APIs proposed by FileMaker 18.
We will discover how it works and learn what the pitfalls are, what the tools to use to set up our calls and how to manage different types of data and scripts. We will create a FileMaker App that operates independently, while managing to exchange data with FileMaker Server.
For many years it was easier to distribute FileMaker applications on iOS using the FileMaker Go or iOS SDK.
For a long time the only option for a distribution on Android was the WebDirect or personalized publication. Last year we saw LiveCodeFM arrive, a tool that is all in all easy to use and versatile. However, there is now a concrete alternative that you need to know: Google’s Flutter.
How LiveCode uses the FileMaker Data API to connect to FileMaker Server. But unlike LiveCode, it’s more complicated to configure, but it has the great advantage that the same Flutter code base can be used on Android, iOS, web and desktop applications.
It allows you to use your FileMaker data with a powerful mobile application development environment to create something totally different from a typical FileMaker mobile application.
In this session we will create a practical example of Flutter application that communicates with FileMaker Server using the FileMaker Data API and then we will use it on all the most used devices today.
One of the most important procedures in any FileMaker solution is data export.
The tool integrated in FileMaker is wonderful for the individual user who develops for himself, but not up to the solutions created by developers for complex realities: the interface is old and allows the user to see “too much”, showing everyone the fields of all tables, increasing the possibility of errors.
In this special event we will see a way to create a developer-friendly tool: modular, flexible, simple to use, fast remotely and with the possibility of exporting recurring exports.
Little is said about it. Too little.
FileMaker provides developers with a free tool that allows you to publish a FileMaker database as an App on the AppStore (no ANDROID) rather easily.
What is the purpose of this tool?
What are the pre-requisites to get the most out of it?
What are the steps to follow and the tricks to use?
But above all: how can updates be managed without causing data loss to the user?
In this session we will see how to create an application for iOS in just a few steps.
In this session we enter the development of the real world, where industry meets software, where it is necessary to interact with the most demanding users, in search of simplicity of use and performance in the most extreme conditions.
Mission critical systems, integration always and in any case, use in mobility, in search of the extra function and the click in less to do before and better.
What does industrial development mean?
How to integrate FileMaker with external databases in any industrial context?
How to use with satisfaction the mobile solutions in an “inconvenient” environment, whether it is factory or warehouse?
The obligatory transactionality in these cases forces us to make very specific choices.
All without losing sight of performance.
We will see how to distribute tasks to optimize system performance between FileMaker and FileMaker Server, with a watchful eye on disaster recovery strategies.
There’s a lot of talk about custom web publishing, iOS, FileMaker Go, PHP and FileMaker Data API deployments.
But FileMaker WebDirect remains the main tool to go to the web almost immediately and without knowing a line of any other code. Not for nothing is the client that is officially recommended for Android.
The fact that it seems “always the same” does not allow the user to grasp the major changes and the incredible improvements that have been implemented in the latest versions of FileMaker.
In this session we will therefore see how to exploit it to the maximum, using procedures and interfaces that enhance its merits and minimize its defects, moving everything possible to the server.
Accounting with FileMaker is a dream of many.
The biggest obstacle stems from the fact that most developers start from a “production” perspective, that is, they see accounting as a module to “add” to the “real” part of their project: normally a developer doesn’t have a clear and operative idea of what are the elements that are needed for an advanced accounting management, and therefore limits everything to a more or less complex first note: as useful as it is, they are a small part of the accounting tools used by a company .
In fact, the perspective in which an accounting program “sees” and manages data is totally different from that of a production-oriented management system. Indeed, the entire procedural structure of the solution is different, given that entities such as orders to suppliers or invoices are not the result of production operations, but of administrative procedures.
In this session we will examine the fundamental elements for double-entry accounting, passing from the printing rules of the accounting / tax registers to the management of the analytical accounting for advanced reports of analysis of the economic / financial management.
We will therefore see how to replicate them in FileMaker with the minimum of effort and how to change the “point of view” on the data in order to create an accounting form, also used in international contexts, to be combined with the production part and such as to also gain the surly signal of an accountant’s approval.
Data separation and interface techniques in FileMaker have a long history: in fact, it was born with version 7 and the first major renewal of the FileMaker engine.
The scenario was then profoundly different: broadband practically did not exist and “remote” work was considered exceptional. The possibility of being able to divide data and interface therefore allowed a great flexibility of updating to the developer, and it was fundamental in some cases.
Today we can have a decent band also from mobile, most of the work is done on remote servers (maybe even by train), and we have the Data API to pass the data, or tools like the Data Migration Tool that allows us to fast data update speed: the data and interface separation regime appears to be a relic of the past.
In reality this is not the case: in this session we will see how it can be used to speed up our work and to allow users greater speed of use even remotely.
Although it does not appear, FileMaker has good transactional bases: the problem is to understand how to best exploit them.
Transactional development offers many advantages:
– greater network speed and less server load, as the data of a record is sent all together
– greater error control, as the data is written only AFTER all the checks
– minor record locking problems
– ease of use of wizards for user activities
– better possibilities to “historicize” data and manage audit trails and rollbacks
– greater standardization – using procedures and screens that are easily recyclable in other projects or areas.
Obviously “there are no such things as a free meal”, so a similar approach (and a lower level of user empowerment) corresponds to more developer work.
But how much greater? Less than you think, once you understand the basic mechanisms.
In this session we will see how to make our transactional solution with minimal effort.
Values lists are born with FileMaker and have not evolved since the advent of the relational engine.
Or at least the management tool offered by FileMaker hasn’t had it, since the way to use value lists has been revolutionized by the ExecuteSQL function.
In this session we will discover how to create virtual value lists, different for each user or even for a single window.
The technique leads to an approach to sessions of use, which allows a great speed and a control on the activities of the users, to use them to manage the procedures, the navigation and the foundset in a transactional (and quite fast) way.
When we talk about curling, we are absolutely not referring to the sports section that we are so passionate about during the Winter Olympics.
In fact, we are talking about cURLing, and in this case the capital letters make the difference: we are referring to the opensource project cURL, which is the main tool for moving data across the web, and is composed of a library (libcurl) and a utility command line (curl).
FileMaker has a long relationship with cURL, since version 12. Many plugins have allowed it to be used since version 7, but only with FileMaker 16 did it go outing and officially supported the project within the InsertDaURL statement (though not entirely).
The “canonical” use of cURL is related to communication with WebAPP (or with FileMaker DATA API), but we can also use it to work in FTP or to send an email: in fact it is the only way to send an email HTML from FileMaker without using plugins, for example.
In this session we will discover the infinite nuances of cURL, how they are supported by FileMaker and the ways in which it allows us to manage data by overcoming the limits perceived in the use of other functions.
The command line (for CLI friends, from the English Command Line Interface) is the oldest tool in the history of personal computers.
Precisely for this reason it has an infinite number of tools available, most of which are free.
How can FileMaker get the most out of the command line?
In this session we will see how a batch file can save our daily work and how a tool like ghostscript can work to convert files or perform complex operations on PDF.
We will then discover how to take advantage of FileMaker tools, even server-side.
When working with a webapp, the simple part is to send the data: for example, to send an SMS, an HTTPS call is sufficient, usually a few lines.
But what happens when the webapp wants to send data, for example when it is necessary to intercept the SMS reply?
A tool exists and is called WebHook: a specific address to which the webapp sends the response, which must be entered into the system.
In this session we will see what are the best ways to create webhooks that show in our management software FileMaker the most used webapp data.
We are not talking about applied mathematics or theoretical geometry, but about something much more concrete and tangible.
How to manage a floor plan in FileMaker?
How to capture a precise point on a map or on any figure in FileMaker by adding graphics or notations at specific points
How to associate precise data, texts or images to these identified points?
In this session we will see through a success story how to provide the user with an effective, simple and above all “mobile” data collection tool.