Today’s post comes from my colleague Barbara Cooney. Here she reports on the PauseOnError 2018.

It was nine years ago that I attended the very first PauseOnError (PoE) in NY at the Ace Hotel. We crammed into each other’s hotel rooms, some sitting on the floor. There we presented and discussed new techniques sharing the challenges and accomplishments we had encountered in our effort to improve our FileMaker skill set. I was an independent developer, and somewhat isolated. So I was encouraged to meet the people behind the screen names with whom I’d exchanged countless discussions on the forums. It recharged me.

PauseOnError Hits the Big Leagues

Two weeks ago, I attended a much more structured and larger PauseOnError, sponsored by the WomenOfFileMaker.  The event was held in the welcoming and creative city of New Orleans. The hotel we stayed at was lush and extravagant and a perfect setting for an intimate gathering of FileMaker pros.

The hotel for PauseOnError was extravagant. Photo Credit:

The hotel for PauseOnError was extravagant. Photo Credit:

The Theme

PauseOnError was organized by the Women Of FileMaker, and the theme they choose was “Stand Tall”.

Martha Zink, Susan Dean Fennema, and Lisette Wilson kicked things off.

Martha Zink, Susan Dean Fennema, and Lisette Wilson kicked things off.

We stood tall by telling our stories from our name tags to an entire session called “Tell Your Story”. Many of the sessions included this theme in their discussion. It was inspiring to hear of others’ journey too and through FileMaker.

Our nametags gave a little insight into who we are.

A Wide-Range of Presentations

The sessions encompassed many topics. The range spanned growing your FileMaker business to leveraging its position as a platform that can integrate easily with other systems. Since joining Geist Interactive, I’ve already been involved in several API integrations. Here I choose to both validate and expand my knowledge in those integrations sessions.

Lots of API topics

In one of the first sessions, Jeremy Upton’s curiosity led him to explore the developer tools available from Amazon to integrate Alexa. Imagine being able to ask your FileMaker database “what were last month’s sales?” And have Alexa answer back!

Sol Rodriguez demonstrated the use of RestFM with Google’s JavaScript Framework, Angular, to quickly provide web-based access to a FileMaker system. His enthusiasm for how approachable this world is for FileMaker developers was contagious. I plan to sign up for the Udemy course he highly recommended.

Chris Irvine introduced us to an alternative to REST, GraphQL, created by FaceBook. This language lets the user limit the data received back from an API call and in doing so, improve performance when latency is a concern.

Overall, what struck me about each of these sessions is each developer used tenacity and trial & error to push through that initial learning curve hump. The message is clear:

  • You can do this too the tools are out there.
  • It’s achievable.
  • You’ve got a community of developers that will support you.

And Other Topics

Taking a break from API approaches, I attended Anton Anderson’s session. It offered instruction on the use of graphical tools such as FlowCharts and ERDs to communicate complex workflows and relationships, so that you and your client share the same understanding.

Mike Beargie demonstrated how to build modular files which allow you to reuse functionality across several solutions, using JSON to pass parameters and results.

Women of FileMaker

The last session that I attended was dedicated to Women in FileMaker. Here, Martha Zink interviewed several community leaders and asked them to share their challenges, achievements and how their attitudes have changed during their careers.


Photo Credit: Credit:

I was struck with the similarities to my own experiences in my 25 years as a women developer in a male-dominated industry. I gained a sense of confidence listening to how they too overcame the need for perfection and crisis of confidence with which many women are burdened. The top developers, as I saw first hand in the sessions I attended, and witness at Geist, learn by trying, making mistakes, revising and ultimately accomplishing their goal. No one gets it right the first time and expecting to do so is self-defeating. As Dave Ramsey of FMPerception fame explained, “errors allow me to see how it can fail, and that is important info to have too.”

A Fulfilling Pause

Poetically, I ended PauseOnError by running into Ernest Koe, one of the founders of the first POE, in the elevator. He was curious of my reaction to this experience of Pause. I assured him that the camaraderie was still there and the excitement of interacting with community leaders hadn’t diminished. I’m more than ever optimistic of FileMaker’s future and my ability to help my clients accomplish their goals. I’m looking forward to DevCon.

Congratulations. You’ve upgraded to the latest version of the FileMaker platform. That’s a good thing. We always recommend folks do that quickly. There’s compelling reasons to keep your app fresh. The FileMaker platform, in its current 17 version state, is exciting and new and quite game changing (again). Let’s take a moment to look at the new features and consider what changes we might make to our current custom apps. Let’s look at the FileMaker 17 features and consider when and where to use them.

When to Change

Most folks would begin using these new features in new custom apps, but I want to explore how we might use them right now in our current apps. We did only a year ago when this when the platform gave us JSON functions and card windows, to name a few. Many folks immediately changed some popovers to card windows.

Of course the changes make sense only if your clients are on the latest platform. And with version 17 of this platform, we find the licensing options are even easier and less confusing.

Why Change?

There are a few good reasons to at least consider changes to your already-working custom apps.

  • First, it’s what we do. When new features come out, we see where we can begin to adopt them. It’s fun and exciting.
  • Second, we can remove our ‘hacky’ attempts to do what FileMaker 17 now includes. The Master-Detail portal rids our solutions of any other self-made or modular techniques. We can use what FileMaker provides.
  • Third, this version includes many ‘more-efficient’ tools for us to use. The Advanced tools, default fields, etc., make our developer-lives easier.

Let’s look at some of the new features and stop for a moment to consider their use in our current custom apps. Some of these are a ‘must’.

FileMaker 17 Features Considerations

The application name change

FileMaker Pro, which most clients had, is no more. FileMaker Pro 17 Advanced is the new name of the application whether or not the advanced features are in place. So we should use the Database Design Report, one of the advanced features, to check and see if we were using Get(ApplicationVersion) to check for “Pro”. If so, we should update those. Our Realtime Developer Intelligence tool, FMPerception can help with that. You can run a DDR and then very quickly open the DDR in FMPerception and find the words “FileMaker Pro” in any place the calc dialog is available.

Use the Advanced Tools

If you’v’e never used the advanced tools, be sure to get a good understanding of them right away. With them, you can further customize your application (custom functions, custom menus), add security (Encryption at Rest, remove Full-Access privileges) and analyze your system (Database Design Report). Check out how to use those tools here.

Get Used to the new Layout Mode

Our design interface is completely changed, and I think that is a good thing.

The Layout-Mode Window. Redesigned.

The Layout-Mode Window. Redesigned.

Yes, it feels awkward at the beginning, but so did riding a bike, and we all learned that. And yes, it does feel a bit scrunched on a laptop. But I think we’ll get used to it and, in just a few months look back at previous versions and wonder how we did anything.

Layout Mode Considerations

Here’s a couple of thoughts and pointers about the layout window:

  • The Inspector panel and Field/Object panels are docked to the right and left side respectively. No more do we have to hunt on our large screens for the inspector to find it buried behind the object layout window (since the latter got called to the front when selecting an object).
  • We can add more undocked inspectors using the menu command View / Inspectors / New Inspector. That might be useful
  • We can hide the docked panels with a shortcut ( Command/Control + I for the inspector, Command/Control+Option/Alt + T for object window, and Comand/Control + K for field panel). This is useful when we are on a laptop and we need a bit more screen space. We can hide a panel quickly to view something, show the panel quickly to adjust something, and move on. With a short keystroke we can hide/show a panel, giving us the exact view we need.
  • The Field and Object windows are together. But pressing one of their short cuts hides BOTH panels. That’s great. I don’t have to first hide the layout object window and then the field panel.
  • We will probably do more scrolling of the layout to adjust it to the place we want. That’s okay. We can also use the zoom controls to focus in on one spot. Well-designed layouts require microscopic attention.

SubGroup Selection

A small but powerful feature, the sub-group selection feature is amazing. I’ve been using it for awhile and can’t even imagine how I could select items in a group. I can select objects within a group and move it within the group.The dotted line around the group shows the boundaries of the group, and it changes as I move the object far away.

The SubGroup Selection

The SubGroup Selection

Default Fields

The default fields feature provides a custom way to auto-build fields in each new table. It is easy to set up and useful. We can set up our development to start using default fields, automating one more part of our development. Or not. Consider also getting rid of them.
The default fields that are included look like this:

Default Fields

You can change these in name and in calculation fairly easily. To do so, shut down FileMaker Pro 17 Advanced and do the following:

  1. Go to the folder where the defaultFields.xml file is saved
    1. /Applications/FileMaker Pro 17 Advanced/FileMaker Pro
  2. Copy that file. DO NOT remove or edit this file.
  3. Open the file in a text editor or something like Visual Studio Code.
  4. Place the xml file in the shared folder:
    1. Windows: <drive>:\ProgramData\FileMaker\Shared
    2. macOS: /Users/Shared/FileMaker/Shared
  5. Open it in a text editor and make changes as necessary. There’s no documentation yet out there, so be careful.
  6. Save the file.
  7. Open FileMaker Pro 17 Advanced. Create a new table and test to see if the fields were created.

To prevent the default fields from being created, simply add a blank “DefaultFields.xml” file in the same shared folder location.

I think this feature is worthy of attention and use. It provides auto-consistency and removes one more step (copy/pasting fields) from one table to another.
But of course you have to consider using this in teams. Each developer that creates tables will need this xml file in the correct location on their computer. That’s hardly a big deal. We do this with plugins, so finding and placing this file in the correct location barely takes time or effort.

The Current Found Set Portal

Throw away your list views. Get rid of them.
Or at least consider it.

The new master-detail or Current Found Set native feature of FileMaker is a game changer in data presentation. Combining a list view and detail view into one layout is a great compact way to get users to their records quicker.

Current Found Set

This feature should be considered strongly in current and upcoming projects.

Current Found Set Considerations

Here are some factors to consider:

  • The current found set portal shows the current found set of records in the current table.
  • The records in this portal are sorted the same as the current found set.
  • The portal has a built in navigation. Click on a row and that record becomes active. (no more list views with hidden buttons that use Go To Related Records).
  • The current record in the portal can be identified with the new function Get(ActiveRecordNumber). Buttons can be hidden (or visible) unless it’s the active record.
  • There’s an active-record highlighter already in place.
  • A current found set cannot show subsummary parts as easily as a list view/report, but there are already doable workarounds.
  • This may be subjective, but this look is more modern.
  • You can put the portal on the second panel of a slide panel object and do some work to ‘hide or show’ the portal.
  • The records in the portal reflect the found set. If you find students in 6th grade, the portal will only show those.
  • Finally, The Master-detail pattern is very common. People expect it.

Should you replace your list views? It depends on how you think of the factors above. (I would).

Take a break

We will come back in the next blog post with more FileMaker 17 Features Considerations.

Developers of any platform love the new shiny things, and we should explore all that FileMaker has in its latest release of the platform. We should learn all about how these features work and how they’re useful. Along the way, we should consider how a new feature may be used in our current apps as well as in the future. And we need to consider and learn quickly, for the next batch of new shiny things is less than a year away!

Welcome to the big leagues. If you own FileMaker Pro 17 Advanced, then you now are able to use the entire set of tools for your development needs. And if you do not yet have this version, you should strongly consider upgrading today. We will explain our thoughts on upgrading in a future post.

You should be excited that you get to be a part of the “Advanced” group. You get to be more efficient with finding the bugs in scripts and enhancing security. And for me, no longer, on the community forms, do I or others have to ask the OP (original poster) what version they use and if they have FileMaker Pro Advanced or not. I only have to ask for the version Number. Half the initial question is removed.

More Tools in FileMaker Pro Advanced

FileMaker Pro Advanced gives FileMaker developers many more tools than they had when using only FileMaker Pro. Everyone who works in FileMaker now has the options to use them. (“options” really isn’t the right word. Developers will come to rely on these tools like they rely on their right hand or their nose to smell).

I’ve been writing about the advanced features for some time. None of these are new features, but they are features that everyone now can access. So take some time and review these old features. Read about FileMaker 17 features here, but also take some time to know how to use all the tools:

  • Data Viewer – a window showing values in fields and variables, as well as a place to check calculations.
  • Debugger – a window that steps you through the script one at a time and allows you to control the flow of the script.
  • DDR – The essential report that identifies locations and uses of layouts, fields, scripts, calculations in your file(s).
  • Developer Tools – an oft overlooked panel that allows you to work with the file as a whole to beef up security, change the file(s) name(s) and much more.
  • Manage Custom Functions – Write your own functions in FileMaker!
  • Custom Menus – change the buttons in the menu bar and add your own shortcuts.

To activate FileMaker Pro Advanced’s features, go to the Preferences and check the box “Use advanced tools”. This requires a restart. Do that and you’re set. By the way, this is persistent. The advanced tools will remain available every time you open FileMaker Pro Advanced.


I look forward to being able to help answer questions without first asking which flavor of FileMaker you have. If you own version 17, you have FileMaker Pro Advanced and all the features that come with it.

I think it is time we stopped getting too worked up about product version numbers. FileMaker is not a Product. It is a Platform. Platforms are different. They don’t really have a product release every 2 to 4 years. They have regular releases of whatever is ready to go.  That’s why I don’t care much about the number 17.  It has great new features and capabilities that once again improve how we approach how we build apps, just like last years big game changer. Let’s take a closer look, shall we?

Missing the Point

I see a lot of bitching about how FileMaker 17 should be FileMaker 16.5 because it doesn’t have enough new features for end users to get a new version number. Frankly, those forum posts are missing the point. First, this release does have several game-changing features and capabilities.  Second, as I just said FileMaker is a platform, not a product. If you know the difference between the two, all this kvetching over a given release and its number seem pointless. We get a new version every year. It always includes new great stuff. The next batch of new stuff is about a year away.

FileMaker 17 Features I won’t be Talking About

Most of them :-). We’ll have other blog posts that will go into more detail on each of the new features and how they work.  In this post I want to focus on just a couple that I think have major implications for the platform and not necessarily because of what they do specifically in your apps, but because of how they might affect how we approach building high-value FileMaker apps for our organizations and customers.

The End Of a Two-Class System

FileMaker 17 Pro Advanced is now the only Desktop client. There is no more FileMaker Pro. That means that everyone has access to the advanced tools:  custom functions, the DDR, custom menus etc. Everyone can copy and paste the code. Everyone can take advantage of RealTime Developer Intelligence Tools like FMPerception and Analysis Tools like Base Elements and Inspector Pro.

There are no more “haves” and “have-nots”. Just “haves”

This means that product developers can no drop the ridiculous work-a-rounds to handle the fact that most of their customers wouldn’t be able to copy custom functions into their files.

Modular FileMaker 2.0 Guidelines when they are released at FileMaker DevCon 2018 will drop the guideline about not using Custom Functions completely. I was famous for advising against Custom Functions in the past because it decreased the likely hood that code could be re-used by other people, who didn’t have advanced. Since it was focused on sharing code, Modular FileMaker 1.0 Guidelines suggested not using them. While I have moderated that position over the years somewhat, but now we can embrace them fully.

Since everyone is on an equal playing field now it will be easier to teach people to share code and build products that everyone can use.

Less UI Hacks, More Business Logic.

I spent years developing workarounds to UI limitations in FileMaker. Back when we got one release every 30 months and they NEVER included new UI widgets and patterns, this might have made sense, but FileMaker 17’s Master-Detail feature has convinced me that is no longer a good use of time.

Over the last couple of years, FileMaker has added major new UI features that change the way you might develop your interface. We have Popovers, button bars, Top Nav, Card Windows, just to name a few. With this release, we get Master-Detail. It no longer makes sense to waste cycles building up massive leaky abstractions like my old version of MasterDetail.

Instead, I think we should focus on the parts of our system that aren’t going to change as much, the data layer and the logic layer. Maybe design systems so you could rebuild the UI at any time, without having to rebuild the data layer and the business logic.

Data Migrations

The fmDatamigration tool is a game changer. Using our soon to be released Otto product, we have fully automated multi-file GB data migrations going from Development servers to Production servers in just minutes. That is not a typo. GB data migrations from server to server in just minutes! The implications of this are massive and wide reaching.

You may still choose to separate your solution into multiple files, there are many reasons to do so. But avoiding data imports no longer needs to be the reason to do it. Becuase you are free from worrying about data imports, you can find different ways of separating that make more sense for your scenario. You might want to make some features more of a self-contained module that can be maintained separately. Or you may shover everything back into one file. It’s up to you.

Live development on production servers has always been frowned upon.  But it was almost a necessity because some systems could take hours or even days to go through the data migration.  That excuse is now gone.  If you run a busy complex FileMaker solution, you should be doing development on a development server, and doing regular automatic migrations.

The Data API is Out of Beta

The Data API is now out of beta and includes a tiered pricing model that fits nicely into the new simpler overall licensing model.  Finally, we have a pricing model that makes sense.

Developers can feel confident about building on top of the new Data API, because it is official, and generates revenue for FileMaker.  I know some folks wanted it to be free so they could get around FileMaker License costs, but really that is a very shorted sighted view.  If you rely on the FileMaker platform you should want the vendor (FMI) to thrive.

Continuous Improvement

This year’s release ( notice how I didn’t say “17” ) includes a number of compelling improvements both to the end user experience and the developer experience. It is another step in a continuous process of improvement. Each year it gets better and better, and we would do well to work that fact into our plans.

Last week, the Adatasol FileMaker Podcast, hosted by Dan Weiss of Adatasol interviewed Todd. He spoke about Geist Interactive: our history, where we are, and things we love.

Dan’s podcast focuses on the FileMaker platform: development, trends and history. It completely makes sense that Todd would join them. Dan asked great questions that got to the heart of Todd’s history in FileMaker development and where we are headed. Here are some highlights:

  • Todd realized that ‘scripts had to work’ during his work at New Millennium while working on their accounting software, Genesis. And If they fail, there needs to be a safe and complete rollback.
  • Database transactions came along (mostly) in FileMaker 7. These are essential to our work.
  • FileMaker is at our core, but we love and use JavaScript a lot.
  • Some of our products have come from great minds in the community. We partner with them in promoting and supporting them.
  • SaaS products work for some folks, but most businesses need and want custom software.
  • We want all customers to have their own custom software. We can provide products, videos, blog posts, presentations for the DIY crowd. Or we can build the client’s custom-development services.
  • FMPerception is our Realtime Developer Intelligence tool. It has saved Adatasol innumerable hours since it is something a developer can review stats about a file at any moment. We use it daily.
  • JavaScript is eating the world. It is supported entirely on the FileMaker platform. There isn’t anything we can’t do with FileMaker and JavaScript in the small- to medium businesses. GoDraw3 uses JavaScript.
  • We are excited about FileMaker DevCon 2018. It’s our favorite time of the year, and the conference is extremely inspiring and important. We can’t wait to be there and be part of the the week.

Thanks to Dan and Nick at Adatasol for talking with us. It was fun. Check out Adatasol and the podcast here.



Have you ever been deep into a complex FileMaker script and realized you need to know something about the structure of the app?  Maybe you need to know where a custom function is used, or what scripts call the script you are working on. What do you do? You can’t stop to go poking around or running some kind of analysis. That will crush your productivity. You need to keep going, but you just need to know where that darn global variable is declared. What … do … you … do? If this has ever happened to you, you need a tool that provides Realtime Developer Intelligence (RDI).

Do you have the information you need to confidently move through your FileMaker Development tasks?  If not, you need a Realtime Developer Intelligence Tool

RDI is Not an Analysis

First off, Realtime Developer Intelligence tools are different from analysis tools. Analysis tools can be very useful. They can provide very detailed, maybe even customized views of your system, but they take a long time to run. To put it another way, an analysis is not something you do while you are developing.  It is something you do before or after you are developing.  Another problem with analysis tools is that they can get stale.  They are only good if they have been run relatively recently.  If they are too old, or if the system has been radically altered since the last run, then they aren’t accurate any more.


Tools that provide RDI have to give you accurate information about the current state of your system.  Not the state that it was last week, but right now. We think they need to have four important characteristics. We like to say they need to be “A2C2”.  RDI tools should be:

  • Accurate
  • Actionable
  • Comprehensive
  • Current

Let’s look at each of these in detail.


This is sort of obvious, but worth pointing out.  Any intelligence tool that doesn’t give you accurate intelligence isn’t very useful.  You need good data to make good decisions. If the intel you are getting is just wrong it could land you in some serious trouble.  If your data says a custom function isn’t used anywhere when it is actually used by dozens of scripts, that is a problem.


An intelligence tool should aspire to give you information you can use to make decisions and take action.  If the information it provides leaves you without any idea what to do, why bother with it all?  If it doesn’t help, it’s just noise.  If you just want to know where a global variable is declared, you don’t want or need to wade through lots of irrelevant information to get it.


If you are only getting part of the story, you are sort of stuck. While it is often true that some information is better than no information, it isn’t always. Having a gap in your intel could cause quite a problem. It is best if you get information that covers the entire field of play.  If we are speaking of FileMaker, and we are, then you want intel that covers more than just scripts, or tables, or just one file.  You need intel that covers all the details in all the files in your entire custom application.


Many FileMaker projects move very quickly. Changes are happening all the time. If the data you are using is a week, or a day, or even an hour old, it could be misleading.  Maybe it was fresh once, but now it’s stale…  You require information that is current, up-to-date, or as we sometimes say, “realtime”.

Realtime Developer Intelligence

Stay in the zone, with Realtime Developer Intelligence

Realtime Developer Intelligence

If you have a tool that gives you Realtime Developer Intelligence, then you know you have A2C2.  You know you have data that is accurate, actionable, comprehensive and current. You have the confidence to move rapidly through your development tasks. You know what you need to know, when you need to know it.  No more guessing.  Just knowing.


While there are many analysis tools on the market for FileMaker, there is only one RDI tool, and that is FMPerception. Nothing else has A2C2 covered as well as FMPerception.  It will get you the intel you need, when you need it. It will not take you out of your flow. You’ll just keep going, confident that you have the right information to make decisions. It is a huge productivity boost.

Please give it a try if you haven’t already.  There is a free, fully functional 14-day trial available for download at

Welcome to GoDraw3: The FileMaker Drawing Tool.

GoDraw3 is a powerful FileMaker drawing tool. Its native FileMaker features gives freedom to a user and flexibility to the developer of the custom app.

Freedom for the User

There is a lot of freedom for a user of GoDraw3 to draw images and store them in FileMaker.

Any user is able to:

  • Create a brand new image or draw on an existing picture.
  • Use drawing tools such as a pen or shape tool inside GODraw3’s drawing canvas.
  • Save the image in one of four possible formats: .png, .jpg, .pdf, or .svg format and use these formats for other purposes.
  • Open an image and re-edit the drawing.
  • Use standard shortcuts to speed up the workflow.

Flexibility for the Developer

GoDraw3 is all native FileMaker.

FileMaker Drawing: All Native

The drawing canvas. All FileMaker buttons, scripts, layouts and other objects

Even though the drawing part of tool is a JavaScript application running in a web viewer the developer has complete control over the implementation and customization of this app. Here are some of the reasons why:

  • The web viewer app is self-contained in a separate file, making it easy to integrate into an existing custom app.
  • The design of the toolbars buttons and other UI elements is all done in FileMaker, so you can completely change how it looks just using FileMaker Layout mode. Don’t want users to create Text, just delete the button. It’s up to you.
  • The buttons all run FileMaker scripts that eventually tell the GoDraw canvas what to do. Once you learn how those scripts work you can customize the heck out of what they do.  You can have buttons that only make blue circles, or Red Rectangle, or insert an image of your Han Solo action figure. You get to decide.
  • The image is stored three ways:
    • in the container in a format chosen by the user (.png, .jpg, .pdf)
    • in a text field as an .svg
    • in a text field as a JSON object
  • JSON is the perfect data format for storing the edited images. With FileMaker’s built in JSON functions you create and parse entire documents if you want.

Because of the native nature of GoDraw3, there are plenty of possibilities for customization. GoDraw3 is completely open a developer to do with it what she wishes.

The Best FileMaker Drawing Experience

GoDraw3 is the best way to draw in FileMaker, saving the image and then editing it later. We’re excited about the potential. We have a lot of thoughts on how it can be used, and we will be sharing those over the next few days. Stay tuned to our blog to learn:

  • Specific use cases for which GoDraw3 would be great.
  • How to fully customize this tool for your custom app.
  • The techniques built into the app.

Learn all about GoDraw3.

Download it for free to try it out. The demo comes fully functional, but does contain a watermark on the drawing. So give it a spin and see how easy it is to draw in FileMaker.

We’ve got something special up our sleeves. It’s an awesome new version of a great product, and it features some great technology. . .

We’re pretty proud of it. Stay tuned!

It’s March Madness time, and we’ve got some great topics this month. Dave Graham and Lance Brandenberg will present for us.

Geist Interactive’s Generator

Dave Graham will share the work Geist Interactive has done on Generator: Using FileMaker to Create FileMaker. We’ll explore all the great features of this wonderful and free tool.

Testable FileMaker Solutions by Lance Brandenberg

With the release of FileMaker 16 and native JSON functions, the ability to create a testable solution has been vastly improved. I will walk you through a simple example of what testing is, and how it can improve your solutions. Most developers have had situations where they need to alter some existing logic, and are concerned that they might alter something with unforeseen consequences. Wouldn’t it be nice if you could ensure that your changes didn’t break existing code? Welcome to FileMaker Testing.

Come join us for these great topics. And as always, bring your ideas and thoughts.

We love FileMaker DevCon. We get to hang with our peeps, and talk about our favorite thing, the awesome power of the FileMaker Platform. That’s why we are very excited to announce that Geist Interactive is a Diamond Sponsor of the 2018 FileMaker DevCon in Dallas, Tx  Aug 6 – 9, 2018. Our team will be there in force, delivering presentations, hanging out in our booth, or leveling up our skills. We hope to see you there.

Training and Sessions

This year three of the team members will be presenting in sessions throughout the week. Here is a list of the topics we bring to DevCon. And be sure to check out the full schedule.

Todd Geist

 Modular FileMaker 2.0

Modular FileMaker is a guideline for writing re-usable code that can be shared between developers or different projects. The web-site was launched more than 4 years ago, and has proved to be very popular. There are over 60 modules published on the site to date. Times have changed. JSON and Card Windows add some of the much needed native features we lacked back in 2013. It’s time for an update. We’ll look at the new updated guidelines and examine several sample modules. We’ll also introduce everyone to how they can contribute to this important free community resource.

Microsoft Office Addons Integration

FileMaker Server and Microsoft Office are a powerful combination. Not only does FileMaker Server OAuth support Active Directory, the FileMaker Data API, provides a way to connect custom MS Office Addons directly to FileMaker data. MS Office Addons are built with HTML and JavaScript, and are embedded directly inside the MS Office suite. In this session, we’ll construct and Outlook Addon that works on Mac, Windows, Web, iOS, and Android, and connects to a FileMaker database to allow viewing and editing data related to the currently displayed email.

Lance Brandenberg

Testable FileMaker Custom Apps

With the release of FileMaker 16 and native JSON functions, it’s easier than ever to create testable FileMaker apps. We will walk through a simple example of what testing is, and how it can improve your solutions. Most developers have had situations where they need to alter some existing logic, and are concerned that they might alter something with unforeseen consequences. Wouldn’t it be nice if you could ensure that your changes didn’t break existing code? Welcome to FileMaker Testing.

Jeremy Brown

JavaScript for FileMaker Developers

JavaScript, the easy-to-read and most widely used language is the only programming language that is natively supported in all parts of the FileMaker platform. The language brings more functionality and speed to our custom apps. JavaScript is very much worth learning. In this course, we will learn JavaScript starting with our vast knowledge of FileMaker. We will focus on scope, variables, and functions, connecting those concepts to what we know already. By the end of the morning, you’ll have many small apps and have a better understanding of JavaScript. Jeremy loves this stuff and is excited to share about it.

This session is a half-day training session that is an additional cost.

FileMaker DevCon

Geist Interactive Team at our San Diego Office

Geist Interactive Booth

In the exhibit hall, we will have a large booth where team members will gladly say hi, offer advice, and talk about our services and products. The larger-than-life Dave Ramsey, author of FMPerception and DamageDetectoR will give entertaining and informative impromptu talks about the FileMaker platform and FMPerception.

FileMaker DevCon Out and About

The entire team will be there for the entire week, so find one of us and say hi. We’ll have the “Geist Interactive” swag, so we will be easy to identify. We want to meet everyone and talk FileMaker! Come to our booth or find us around the exhibit hall or in the sessions or by the pool, and we’ll happily chat about the platform we love.