For our German speaking clients we have a workshop day:
In Zusammenarbeit mit der DenkForm GmbH bieten wir eine Schulung zum MBS Plugin an. Am 6. Dezember 2018 (auch 7. März 2019) können Sie in Hofheim am Taunus an einer eintägigen Schulung teilnehmen. Lernen Sie die über 5600 Funktionen einmal näher kennen und wie Sie sie effektiv einsetzen. Sammeln Sie Ideen und verbessern Sie ihre FileMaker Lösungen durch den Einsatz unseres Plugins.
Das Monkeybread Software Plugin für FileMaker stellt eine vielseitige Erweiterung der eigenen Datenbank dar. Der Kurs bietet nicht nur einen tiefgreifenden Überblick in die Benutzung und Entwicklung, sondern bietet auch die Chance das Plugin günstiger zu erstehen.
Einführung in das MBS Plugin
Überblick über die Funktionsbereiche
Neues im MBS Plugin dieses Jahr
Rundgang durch ausgewählte Beispiele
Gemeinsames Implementieren von Plugin Funktionen in eine Datenbank:
Upload/Download mit CURL auf einen HTTP/FTP Server
Ausfüllen eines Formulares auf einer Webseite
Adressbuch und Kontakte abfragen bei Mac OS X.
Fragen und Antworten
Die Teilnahme kostet 119 Euro inkl. MWSt. und Verpflegung.
Details und Anmeldung bei der Denkform.
Im Anschluss geht es noch zur Pizzeria zum FileMaker Stammtisch Rhein-Main.
An jedem ersten Donnerstag im Monat findet ab 19 Uhr der FileMaker Stammtisch Rhein-Main statt, zu dem jeder herzlichst eingeladen ist.
Zahlreiche FileMaker Vorträge am Abend, Empfang und einem unterhaltsames Special am Ende.
Bitte bald anmelden, denn der Platz is begrenzt. Das Programm startet gegen 17:30 Uhr und der Eintritt kostet 50 CHF.
MBS Plugin Schulung
Wir bieten eine MBS Plugin Schulung für den gleichen Tag um ca. 9 Uhr im gleichen Hotel an. Für unsere Kunden haben wir ein Programm zusammengestellt speziell für die Anforderungen in der Schweiz:
MBS Plugin Überblick für 2018.
QRCodes für Schweizer Einzahlungsscheine nach ISO 20022.
FileMaker Migration Tool
MBS Shell Funktionen um das Tool zu automatisieren
SmartCards auslesen am Beispiel der Schweizer Krankenversichertenkarte
Word-Serienbriefe aus FileMaker
Fragen & Antworten
Weitere Themenwünsche bitte baldmöglichst an mich schicken.
Kostenbeitrag: 150 CHF inkl. Mittagessen.
Der Filemaker Stammtisch Rheinland findet an jedem 1. Dienstag im Monat um 19:00 Uhr statt.
Der nächste Termin ist der 6.11.2018.
Der Stammtisch findet in Bonn Beuel, im Portofino, St. Augustiner Str. 129, statt.
Themen des nächsten Stammtischs:
Nutzung von Google Diensten wie Google Maps, Google Charts, Entfernungsberechnungen etc. mit Filemaker.
We got recently a new function Text.MergeFields to merge field values into a text block. This is useful for placeholders in a text sent by email. You just put a <<FirstName>> in the text, the plugin sees the << and >>, takes the text between and looks for a field matching the name. The function definition is:
MBS( "Text.MergeFields"; Text; Flags )
We got a few flags to process. If Flags includes 1, we recognize field names. This can be a simple field name in the current table or a field from related tables with Table::Field notation using two colons.
Add 2 to Flags in order to allow variables. They need to start with one or two $ symbols. We evaluate the value and use it for the text. Variable names can contain spaces, but we don't recommend that.
Next add 4 to allow general expressions. This allows you to call all functions in MBS and other plugins as well as all FIleMaker functions. Great for using some Get functions, but if the user can change this themselves, they can do a lot of damage. If needed, we could maybe add a mode for only allowing Get functions? Let us know if you need that!
If you need values to be properly encoded as HTML or XML, you can get that by adding 16 for XML and 32 for HTML to the flags.
The new function is great for emails. You can have a template referencing fields and fill them when building the email. You could use fields from he current record of the customer you send newsletter to and put in some variables additional content to include. Please try it soon. Coming for version 8.5 and already in the betas.
This is a PDF preview in Microsoft Edge. The PDF in question uses an OpenType font with postscript outlines with the variant without CID Font operators and this format is not supported by the Microsoft Edge PDF viewer.
For MacOS, the preview app shows the PDF, but when you print it, you get an empty paper.
We got a workaround for using this type of font with DynaPDF functions in our FileMaker and Xojo Plugins. So if you like to use such a font and get a working preview above, you need to not use the unicode encoding, but pick one of the 8-bit code pages like 1252.
Query the properties for font via GetSysFontInfos (Xojo) or DynaPDF.SysFontInfo (FileMaker) and check what you get back for BaseType. If the base type is OpenType. If it is open type and CIDOrdering property is empty, please don't use unicode code page for loading that font.
Or as I assume most clients do, is to trash the font and use one with proper character collection information. Otherwise having a checkbox to fall back to 1252 code page could be a checkbox to include for PDF output.
There is currently no direct way to tell SQL to use the current found set as condition for a query. But with the GetNthRecord function from FileMaker and the FM.Loop function in MBS FileMaker Plugin, we can build a list of IDs and generate automatically the SQL condition to use the found set.
The following line queries a list of IDs from current record:
As you see we define variable and count it from 1 up to the number of records in found set. For each loop iteration, GetNthRecord is called to query field named Contacts::ID and we get back the list of IDs like this:
We can change the calls to produce the right list for SQL with IN operator. We add some text before and after and replace the new line with the comma going between values. The new loop call looks like this:
"(ID in (" &substitute(MBS("FM.Loop"; "index"; 1; Get( FoundCount ); 1; "GetNthRecord ( Contacts::ID ; index )"); ¶; ",")& "))"
The text returned may look like this: (ID in (2,3,5,6,7,8))
Please note that for UUIDs you may need to add quotes to get them in quotes, e.g. like this:
"(ID in '" &substitute(MBS("FM.Loop"; "index"; 1; Get( FoundCount ); 1; "GetNthRecord ( Contacts::ID ; index )"); ¶; "', '")& "')"
The new list has quotes for the ID values: (ID in ('2', '3', '5', '6', '7', '8'))
Next we can build a SQL line using the IDs and query another field like the last name:
MBS("FM.ExecuteFileSQL"; ""; "SELECT \"Last\" FROM Contacts WHERE (\"ID\" in (2,3,5,6,7,8))")
As you see we put Last in extra quotes as last is a reserved value in SQL. In general it doesn't hurt to put all field and tablee names in quotes, so the SQL works for all names including those with spaces. The field used for ID may also need to be quoted and if you use UUIDs, please put values in single quotes.
One little check is required: Please make sure your found set is not empty before using this. Otherwise you end with an error message from FM.Loop or invalid SQL.
PS: With Command-Option-C you can copy expressions with color from the calculation dialog.
For the upcoming 8.5 release of the MBS FileMaker Plugin, we got new functions to create a SSH tunnel from within FileMaker. You can connect to a server via SSH (IP or Domain), authenticate with your password or better your private key and start a tunnel to forward a connection from one side to the other.
This is great to for connect to MySQL server, which is not exposed to the internet. You connect to your web server via SSH and than forward port 3306 from your local machine to port 3306 on the remote machine. Once the tunnel runs, the SQL functions in our plugin can connect through the tunnel to the remove database server.
For details, please see the SSH.Tunnel.Run function to start the tunnel and SSH.Tunnel.Messages to see debug messages. Please don't do anything with the SSH session while the tunnel is running. But you can of course run multiple SSH sessions in parallel to run shell commands or several tunnels.
We had this implemented earlier this year for Xojo (see SSH2TunnelMBS class), but when I mentioned at the FileMaker conference that I have the code to do a tunnel, I was quickly asked to port this to the FileMaker plugin, so here it is.
For testing, we used both the Smart Card Reader from König (left) and the SmartTerminal ST-1144UB from Cherry (right). Both do the job with a little difference. For the left device, you can connect and query status, even if there is no card. The right one only allows to connect when you have a card inserted. Other readers work probably as this uses a standard interface and drivers are built into the operation system.
For Xojo we got the new CryptoTokenKit classes in MBS Xojo Mac64bit Plugin for the modern way Apple likes to handle this with asynchron operation and delegates. Beside this, we also go the older cross platform way via PCSC API and the ReadFile method in and SmartCardMBS class.
Whatever function you use, you can pass the right file ID and read the files you need from the smart cards. We also got a function to split the data into the parts. See SmartCard.SplitValues for FileMaker and SmartCardMBS.SplitValues function for Xojo.
Just in the middle of the seven FileMaker conferences in Europe. Three are done (Dutch, German and Italian) and three are to start this week (English, Spanish and French). And today the conference in Sweden started with over a hundred attendees:
Next I will travel to London for the English conference tomorrow after my MBS Plugin session.
For Malbun we brought our usual posters and decorated a table with papers:
Please come by to say hello, get a pen, some gummy bears and the cool MBS pocket knife (okay for air travel).
The coupon code for our web shop with 20% off from all licenses is FMK2018 this year and valid til end of October.
Diese Woche startet hier in Malbun, Liechtenstein die deutschsprachige FileMaker Konferenz mit Teilnehmern aus mindestens fünf Ländern. Ich hoffe ihr kommt nicht nur zur Konferenz, sondern nehmt euch auch einen extra Tag frei um die schöne Berglandschaft zu genießen.
Zu Fuß oder per Seilbahn kann man auf den Berg Sareis kommen und die Aussicht über das Tal genießen. Der Blick geht weit nach Österreich und die Schweiz rüber. Ab der Kapelle in Malbun kann man über den geschotterten Weg in ca. 4 km bis zum Café an der Bergspitze laufen mit moderater Steigung.
I visit the German conference in Malbun (Liechtenstein), the Scandinavian conference in Gothenburg (Sweden) and the English conference in London (United Kingdom) this year. And for the German conference, Stefanie will join me to help on the booth and with our training day on Wednesday.
See you there!
Greetings to the people in Gent, which start the FM Summit today.
With last plugin release we enabled the option for CURL to disallow you passing user name and password. As URLs are sent to proxy and may be logged at the web servers, we prefer to not include credentials in the URL. And if you use the email address for user name, the name in the URL never worked.
So for the future, please separate them and put the credentials in the relevant options:
Today a client sent me his email script using our plugin. It is based on one of our examples, but got quite a few enhancements.
First like with every professional developer, you see a few comments about what it does and where data is coming from. Also changes are logged at the end. Part of the standard setup of the methods is to disallow user abort and activate error capture to avoid error dialogs.
All the configuration details are not part of the script, but come from a configuration table. For tracing the soluton, a trace script is called to log what happens. Results from sending emails are stored in the table, so you can check for each email whether it worked and what the error message is. Please read the script below:
One of our clients asked how to add a Drag & Drop area on the layout to receive file drops.
Well, the obvious answer is to copy everything from DragTest Windows.fmp12 to their solution and enjoy it for both Mac & Windows. But it's not that simple as you need to know where to look. So here a step by step solution.
Before you start, please make sure you have a recent plugin version. The Drag & Drop features for Windows were introduced in MBS FileMaker Plugin 8.1, but we got bug fixes later, so best is to use current 8.4 release.
Add placeholder rectangle
First in our DragTest Windows.fmp12 file is a picture used for the drop area. The picture is there twice. Once assigned to the rectangle in the layout and second in a global field. So add the DropLogo field to the layout and you can export the image named "Drop-Files-Here-extra.jpg".
In your solution, you may find a layout where you like people to drop stuff. This should be a layout where you would enable Drop in one trigger and than disable it when the user leaves the layout.
To the layout, we add a rectangle area in the header for the drop. Our image is 500 x 224, so our rectangle should be 250 x 112 points big to use 2x image for sharp picture on high resolution screens. In the inspector for fill option, please select picture and select the image file. For the aspect ratio, please choose "Scale to Fit" below. In the first inspector tab, please give the rectangle a name, e.g. "drop".
Please add a global container image named DropLogo. Put it on the layout and import the image here, too. After the import, you can remove the global field from the layout. We need this image later in the script. It's a good idea to actually have two images, one of drop off and one for drop on. This way you can see whether the plugin is working.
Lets add the first two scripts. Please add an empty script named "FreeDrop" and one named "Setup Drop". The names can be different, but you must be consistent and later use the right names in the function calls. For the layout, please edit it and go to the Layout Setup dialog. There pick the SetupDrop script for the OnLayoutEnter trigger. Connect the FreeDrop script with the OnLayoutExit trigger. For debugging you may need to run them directly without trigger.
As you see we plan to keep the reference number for the drop area in the global variable $$dropView. If it is a number bigger than zero, we call DragDrop.Release function and free it. Than we clear the variable. With the If you can run the script several times without problems, e.g. call it before doing an action, which needs the drop area removed.
Now we add lines for the SetupDrop script. Don't type it, but please copy & paste from our example database. The script looks like this:
We start by creating a new drop area control. We pass in the name of the window. The plugin than looks in the window list to find it, so the name should be unique. With "drop" we specify for which layout object to look for. The plugin will query coordinates from FileMaker and try to place the control as good as possible over the existing layout object.
Next line we declare what we want to receive. This is usually file and only applies to Mac where we can choose between receiving text, pictures or file and get the right cursor. With DragDrop.SetDragActionHandler we define which script to call when something arrives. We pass current file name and the script name DragAction. We set the cursor to copy (value 1) and than set the image of the container field.
You can test this already. If you run the SetupDrop script, the image fo the drop area should change a bit to show the image from the global field. If you run FreeDrop script, it should revert back.
Our example needs the following fields. First a container field for the actual file data we receive. Than a text field for the file path or name to show to the user. And for our example we also have a description field to show how we got the file, but you don't need that.
So please add the container and text field to your database table or reuse existing fields there and change the following script.
Here we have now the big script to handle the drops. The script has 4 sections. First a bit of setup to get the drop view ID from the script parameter and prepare the names list as variable with just an empty entry.:
Set Variable [ $dropview ; Value: Get(ScriptParameter) ]
Set Variable [ $names ; Value: ¶ ]
Second part accepts file paths dropped on our rectangle and imports the files. If we get a file path and the file is not yet here, we wait a second to the other application write it. Anyway we read file path and put file name in the names list. This way we can avoid duplicates if a file is provides two ways on Windows. Next we create a record and add the file as container value to the container field. The loop runs til all files are processed:
Set Field [ DragTest::Description ; "Got via path list" ]
Commit Records/Requests [ With dialog: Off ]
Set Variable [ $index ; Value: $index+1 ]
Exit Loop If [ $index = $count ]
The third part of the script checks for file descriptors. The MBS plugin can receive promised file drops. For Mac, we convert them to real files for you and provide them with the path list above. For Windows we get file descriptor which describes the file. If you ask the plugin for size, path or data, the plugin will request the file and the data is transferred in memory without disk usage. The file descriptor may describe a file on disk or in memory, so we handle both in the script: Either we get a file path and read the file or we get it a container and put it in the field right away:
# Check for a file descriptor coming with Drag & Drop
As you may have seen the videos from FileMaker DevCon 2018 in Grapevine, Texas are planned to arrive soon.
The DevCon 2018 sessions by track website shows 9th October 2018 as release dates for the videos.