FileMaker Data API

DrSnip: Web App Patient Portal

Dr. Snip is a vasectomy clinic that needed a web form for patient inquiries that tied into their FileMaker system. We used FM BetterForms to build a complex Web app very quickly.

Creating A COVID-19-Safe Signing System For FileMaker Go

Due to COVID-19, we recently had to invent a way to sign forms on-site without sharing devices. Part of the conversation went like this:

He thought for a minute and replied, “Here’s what we’ll do. We’ll make a way for a user to sign a form without ever touching the iPad. How about we create a record just for signatures? We can send a link out to the client that will open a WebDirect interface. It would present them their signature record on their own device, and boom! Touch-free signatures.”

“Brilliant!” I said happily. “Let’s go! I’ll grab some pizza.”

Container Data and the FileMaker Data API

Back when I was learning about the FileMaker Data API, I had trouble finding any information on how container data was handled. Oddly, the upload information in the Help documentation seemed far more complete than the download information, especially considering the download information isn’t even it’s own section. It’s a note in the URL And Data Format notes section. In essence, the note is: You will get a URL referencing the location of the container data, which is somewhere on the internet. You’re welcome. I ended up utilizing the Base64 Encode And Decode functions in a way that I’ll forever keep as a tool in my developer’s toolbox. If you’re not familiar with these functions, they easily convert images into text and vice versa.

Scroll to Top