MightyData

FileMaker and WordPress Consultants

  • Company
    • About
    • Contact
    • Team
    • Artists
  • Services
    • Consulting
    • Development
    • Our Process
    • Coaching
    • Training
  • Results
    • Customers
    • Success Stories
    • Testimonials
  • Blog

Happy New Year!

January 7, 2016 by Kirk Bowman Leave a Comment

It’s been a while since we’ve posted a blog article. We’ve been making some changes in our business and wanted to fill you in on what we’ve been up to.

First, MightyData is moving away from software development and into business and technical consulting. Don’t worry – if you are a current customer, we will continue to serve you. MightyData is still a FileMaker Business Alliance member.

However, we are transitioning away from straight development work. Starting this year, we will begin sharing more strategic messages through this blog and fewer “how to” technology-based posts.

Second, we’ve been working on creating another brand, Art of Value. This is the only time that we will talk about Art of Value through the MightyData blog, but we thought you might be interested in hearing what we’ve been up to on that front.

Art of Value is a business consultancy that teaches people how to set themselves free of timesheets, and serve customers better, all while increasing income. We can show you how to implement a new business model to accomplish those goals. We have almost 80 podcast episodes with great content.

Tonight at 6:30pm CST, we are hosting a free webinar. Sign up and see what we’ve been up to.

Here is what you can learn on the webinar:

  1. how to overcome the biggest obstacle to increasing your income. (It’s not what you think it is.)
  2. how to implement a business model that, once you embrace it, makes it possible to experience bigger increases than you can even imagine.
  3. a strategy to increase the probability of your customer saying “yes” by 50%.
  4. how you can charge a higher price and have your customers thank you for it.

There will be a couple of free gifts for you on the webinar, but you need to sign up and show up to collect your gifts.

We wish you a very successful 2016!

Filed Under: MightyData Culture, News, Pricing Tagged With: Consulting, value pricing

The Price of FileMaker 13

April 29, 2014 by Kirk Bowman 61 Comments

The Price of FileMaker 13

In a recent post, The State of FileMaker 13, a couple of readers wrote comments expressing  frustration with the licensing costs of FileMaker 13, especially FileMaker Go. Since it seems to be a controversial topic, here are my thoughts.

The Price of FileMaker 13

A History Lesson

Before FileMaker Go, the FileMaker family consisted of FileMaker Pro (client) and FileMaker Server. FileMaker Pro was sold (and still is) by the number of installs, starting around $300 per computer. FileMaker Server was sold for a fixed price of  $1,000.

Then in 2010 (circa FileMaker Pro 11), FileMaker, Inc., (FMI) released FileMaker Go. It was originally two separate apps, one for the iPhone and another for the iPad. The price of the iPhone app was $20 and the iPad app was $40. Each app was a one-time purchase for unlimited use.

$20/$40 is considered expensive for apps in the App Store. Although there are other apps with premium prices, these prices did deter some customers from using FileMaker Go. It also made it challenging for companies to submit payment and then install the app on multiple devices through iTunes.

The Next Step

When FileMaker 12 was released, FMI made FileMaker Go 12 a free app. Anyone could download it from the App Store. This was a great marketing move because it removed two significant barriers:

  1. You did not have to pay for it to test it, and
  2. Anyone could and install it through the App Store.

During the FileMaker 12 product life cycle, customers got used to using FileMaker Go for free. In fact, if  your database was uploaded to a hosting provider, you could deploy a FileMaker solution to iOS devices for as little as $29/month. This was great for users because anyone could get up and running for almost nothing. And, it was good for FMI, for a while.

The market penetration that FMI received from making FileMaker Go 12 was good for the company and the community. However, if you know anything about pricing (one of my favorite topics), a penetration strategy is not financially stable indefinitely. At some point, the company must pivot and make a return on the investment (ROI). And that is what FMI did with FileMaker Go 13.

FileMaker Go Today

At the 2013 FileMaker Developer Conference, FMI showed a preview of the FileMaker 13 product line. Many of the new features were designed to help developers and users create more effective mobile solutions. There was also an “Under the Hood” where Dominique Goupil, president of FMI, suggested the licensing model for FileMaker 13 would evolve. Although he did not give specifics, it was a heads up that a change was coming.

When FileMaker 13 shipped, the licensing for FileMaker Pro (per install) and FileMaker Server (fixed price) remained the same. FileMaker Go remained a free app to download. So, users could continue to use it for a stand-alone solution at no cost. The change was the price to connect to FileMaker Server.

The new licensing model uses concurrent connections. If you have an average of 5 users connecting to FileMaker Server with FileMaker Go, then you need to purchase 5 connection licenses. If you have an average of 10, you need 10 licenses. The cost per  license starts at $180 per connection depending on the total number of licenses. If you need more connections, you can purchase them directly in the FileMaker Server admin console. (FMI is also using the same licensing model for WebDirect.)

Is It Fair?

This is the real question people are asking. On the surface, moving from paid to free, back to paid seems like bait-and-switch. However, you can also view it as FMI experimenting with how to price a new product. Think about your own business. How do you learn to price something? You experiment, or at least you should. FMI had to try different strategies to find the right one. Also, it is completely fair for FMI to recoup its investment in FileMaker Go.

If it is fair, then the next question is, “Does the new licensing model work for you?” First, realize there are a couple of different ways to buy licenses. The $180 per concurrent license is for a volume license (one-time fee). FMI also offers annual licensing which gives you the ability to pay a reduced price each year. The annual cost for a concurrent license starts at $60. If price is your objection, then consider annual licensing.

Second, what is the value you receive from using FileMaker Go? Does using your solution on the iPhone or iPad create more revenue than the cost of the volume or annual license? I would suggest you are probably making at least 10 times (or greater) the revenue vs. the cost. What is the benefit to your gross revenue, gross profit, cost savings, productivity, customer service, quality of life, etc., from your mobile solution? If you do the math, I think you will see things in a different light.

Do you agree or disagree? Do you think FMI is right or wrong with the pricing of FileMaker 13? You can leave a comment using the form below.

Filed Under: Pricing Tagged With: FileMaker 13, FileMaker Go, Licensing

How To Write a FileMaker Module

April 24, 2014 by Darren Burgess Leave a Comment

Hopefully by now you have found your way to ModularFileMaker.org and have checked out the many FM modules available to bolt onto your database solutions. mFM has endeavored to create standards and best practices for writing portable code modules that allow developers to incorporate new functionality into their database applications. The focus is entirely on portability.

While you are visiting mFM, take a look at the modules I have authored:

  • Propa-gator is a simple module for record creation. It allows you create a record in any context and set any number of fields in that new records. I wrote about this module in the MightyData blog as well.
  • My second contribution to the library is Accounts. This module offers wide range of functionality related to the management of user accounts in a single or multi-file FileMaker solution. It is currently at version 1.3 and has benefitted hugely from community input.

Have you considered writing your own module and submitting it? If so, I say go for it. Even if your idea is already implemented, the library of modules will benefit from a variety of solutions to the same problem.

Before you begin your project, I thought I would share some tips for helping you get started and moving on developing a module:

  1. Read the guidelines. Believe it or not, there is not much to them, and they are just that – guidelines. The guidelines are there to help you structure your solution and begin to grok the mFM way of thinking.
    Script organization and name spacing in fmModule
  2. Float your idea to the community and ask for help. There is a Google group devoted to mFM. Check out the various convo threads or perhaps start your own.
  3. Download a few published modules to get an idea of how to structure your scripts.
  4. Check out some of Todd’s videos on the subject of modular coding in FileMaker here and here.
  5. Start. Maybe that seems obvious, but it is worth mentioning that once you start the project, if you are passionate about it, it will take on a life of its own. I probably put 40+ hours into Accounts. It was well worth it, as now I have feature rich and robust Account management module available to any customer solution with just an hour or so of integration work.
  6. Ship. Don’t let your project get to 95% and then stop. Get it out to the community. I got great feedback on the modules I released that made them vastly better. You can pretty much guarantee that you won’t think of everything.
  7. Ship version releases. Your 1.0 does not have to be customer production ready. (BTW, check out the readme in the Accounts module. I use the readme to track feature requests, bugs and a proposed development roadmap).
  8. Eat your own dog food. Once it is ready, integrate your module in a customer solution, following your own integration documentation. I was shocked at how awful my initial documentation was. And I discovered bugs and new features by putting the solution out in the wild. (Just make sure you can easily roll back the solution, in case your module really isn’t truly ready for production.)
  9. Keeping eating that dog food! Integrate into more customer solutions – each time will reveal new possibilities.

Well, I hope that has inspired you to contribute to the mFM cause. The FileMaker community needs your ideas and your development skills will benefit from the discipline it takes to plan, develop, ship and improve a FileMaker module. I would love to hear about your ideas or feedback on published modules – ping me here in the comments or on twitter (@darrenburgess).

Filed Under: Rapid Development Tagged With: Development standards, FileMaker 13, FileMaker module

The State of FileMaker 13

April 17, 2014 by Kirk Bowman 14 Comments

FileMaker Pro 13

If you are a customer or developer using FileMaker Pro, you probably know the latest version, FileMaker 13 was released in December 2013. I have not written about this release yet, because I wanted to reserve my comments until I had time to work with it. Now I have. So, what is the state of FileMaker 13?

FileMaker Pro 13

First, let’s talk about what FileMaker is at the core. It is a client-server database platform for making custom business applications. For years, FileMaker has had a desktop application (FMPro) and a server application (FMS). Then recently, FMI added an iOS application (FMGo). So, now the “client” part of client-server includes the iPhone and iPad.

Web Publishing

Of course, FileMaker also has a web publishing component in the server application. Instant Web Publishing (retired in FileMaker 13), was designed to help a FileMaker developer with minimal web experience create web access to a FileMaker solution. Custom Web Publishing was intended for the traditional web developer who knows HTML, CSS, PHP, etc. to create custom web apps for a FileMaker backend.

In FileMaker 13, Instant Web Publishing was replaced with WebDirect. WebDirect is intended to bring the desktop experience of FileMaker Pro to the browser. WebDirect is a new technology, a 1.0 release. In some ways, it is similar to when FileMaker Go released. It is a new type of “client” except it does not require installing any software because it runs in the browser. As with FMGo, will require some time to mature and for developers to figure out best practices.

Client-Server

So, where does this leave us? I go back to what I said earlier. FileMaker is a client-server database platform for making custom business applications. Currently it has two rock-solid clients, desktop (FMPro) and iOS (FMGo). You could also consider Custom Web Publishing a third client except that it requires development skills outside the normal FileMaker toolbox.

FileMaker is not a true SaaS application. It requires a client on the local device. You can put the server application on a cloud server (hosting provider, AWS, Rackspace, etc.). Then, if you have a well-designed solution, you can access the application “in the cloud” using the client on the local device. Is this a web-based app? No. But not every business needs one.

What is my point? Let’s be honest, and not ashamed, of what FileMaker really is and is not. Be honest with yourself and your customers about whether FileMaker is the right fit. If it is, use it. If it is not, have other options to offer the customer. Do not try to fit a square peg into a round hole. It is a disservice to the FileMaker platform and the customer.

Wrapping Up

Back to FileMaker 13, the latest advancements in the platform — including the layout theme/style engine, the new layout objects (popover and slide control), the improvement in iOS functionality, and the server enhancements like Perform Script on Server — are significant steps forward. However, these do not change what FileMaker currently is: a client-server database for custom applications on desktops and iOS.

Learn how to determine whether FileMaker is a good fit for your project. Use it for its strengths and work around its weaknesses. (BTW, all development platforms have weaknesses.) If you are not sure how to do this, get help. The worst thing you can do is declare “if it cannot be done in FileMaker, it is not worth doing.”

That is my take on the state of FileMaker 13. What do you think? You can leave a comment using the form below.

Filed Under: Web Development Tagged With: FileMaker 13, FileMaker Go, WebDirect

Hiding Objects in FileMaker 13

January 27, 2014 by Anders Monsen Leave a Comment

Calculation for hidden object in the Inispector

In versions of FileMaker prior to 13 developers have used creative methods to hide objects on layouts. Using conditional formatting and making the font size 300 or higher has rendered the text invisible to users given certain conditions. Hiding tab panels by making them “invisible” required more creative options, which applied only to tab control panels, and generally applied to an “all or nothing” state.

Conditionally hiding objects not only is easier in FileMaker 13, but applies to a wide range of objects, and enables greater flexibility when to hide and show objects. The new object behavior method in the Inspector applies a Boolean (true or false) condition to show objects. Although this means that the visibility state of an object can change on the fly, in order to trigger this change it needs to be prompted by a Refresh Window or Refresh Object action.

Calculation for hidden object in the Inispector

Objects hidden using this new method are identified with a new “badge” in layout mode, an icon that looks like an eye when enabled in the View menu.

Badges for conditional formatting and hidden objects

Show menu (right-click) for badges

While using an “invisible tab panel” method (see above) appears to work, it requires far more effort than the newer method. First, the prior method requires that each tab panel have the same conditional formatting. Then, each state of the panel (Active, Inactive, Hover, In Focus) must be considered. Borders must be removed. Each layout themes may have additional considerations that need to be taken into account. Inconsistencies may appear if the solution was created in 12, then opened in 13, with strange artifacts causing tab panels to display. Also, if created in FileMaker 13, occasionally the text on the table panel in layout mode appears only for the active panel, and in find mode some of the panel’s text might also appear.

Using the hidden object attribute not only works on text and tab control panels, but also other objects like portals and fields. These become completely invisible when the condition is true.

A few things to consider:

  • For tab panels this is an all-or-none deal – hiding one tab results in all tabs being hidden.
  • Table view will not hide objects – fields become visible if the user switches to this view; conditionally hiding obejcts is not intended as a new security model.
  • Scripts can still go to hidden objects, rendering the FileMaker 12 hidden tab method obsolete.
  • Individual objects can be hidden inside portals. Annoyed by icons appearing in portals where there is no data? Hide them.

The new method gives developers more control in terms of conditionally hiding or displaying text and objects on layouts. Rather than using a series of work-arounds we now have native, built-in behavior.

Filed Under: Layout Design Tagged With: Conditional formatting, FileMaker 13, Layout objects

Calculations for Custom Dialogs and Tab Names

January 15, 2014 by Darren Burgess Leave a Comment

Calculation for tab name

FileMaker users and developers should note the addition of calculated Custom Dialog buttons and Tab Panel names as one of the new features of FileMaker 13.

While these are relatively small changes, we are pleased to see FileMaker continuing to expand the incorporation of the calc dialog throughout the FileMaker development environment.

Here is example as implemented in the FileMaker Server 13 sample file that comes installed with FileMaker Server.

Calculation for tab name

Customize by Language

This is great news for helping developers create language-localized solutions. In particular, calculated tab panel labels no longer need to be overlaid on the panel, reducing layout maintenance. In this case, tab panel names are now calculated, the values drawn from a table of translated labels in multiple languages. The sample file checks the application language on start-up and sets a global field that drives the connection to all of the tab panel, field and button labels.

I made a quick modification to the sample file that allows the user to change the language, updating all of the labels on the fly, just to illustrate the point:

Field labels in Japanese language

Custom Dialog button name definition also got the benefit of the calculation dialog.  Note in this case I am using a field, the Project Name, as the calculation for the button in the dialog.  This is a simplistic example, but illustrates that the dialog is aware of the table occurrence context when it is generated (and also has access to table occurrences related to such):

Calculation for button name

One final note regarding the buttons on the Custom Dialog:  They are still limited in size and will not display text beyond 11 or so characters.

Filed Under: Calculations Tagged With: FileMaker 13

Popover Buttons in FileMaker 13

December 4, 2013 by Darren Burgess 7 Comments

Popover button setup

FileMaker 13 brings with it many new innovative features. Building on the new design space innovations created in FileMaker 12 and a continued focus on database tools for mobile, FileMaker 13 offers a new layout object dubbed the “Popover Button”.

Example of popover button in starter solution

You may recall some months ago I wrote about pros and cons (mostly con) of using tab panels to hide and display pop-up content to assist in data entry and display.

The Popover Button

Well, now that rather kludgy technique has been rendered mostly obsolete with Popover Buttons.  A Popover Button is a new layout object that creates a pop up within which you can place layout objects. This design pattern is seen frequently in the software, web, and mobile design worlds these days, and we are glad that FileMaker is keeping up by providing a simple tool to create this effect. What’s more, Popover Buttons can be used across the FileMaker platform: they work in FileMaker Pro client, FileMaker Go, and through a browser using Web Direct.

Here are just a few ideas of how we might use this new layout object:

  • Display related or secondary data
  • Display container data in a larger format
  • Display additional button choices that don’t fit on a layout
  • Provide the user with a popup to select a record for related record creation
  • Display help text throughout a solution

Creating A Popover Object

True to FileMaker form, creating Popover Buttons is simple.  They are created from the Toolbar object that also creates buttons. You can simply click and hold to toggle between Button and Popover Button.

A Popover Button can then be added to a layout just like a regular button. Once placed, you can click on the button in layout mode – this reveals the popover – and then content can placed within it, just as you would with a tab panel.  Here is a screen shot from the Invoices starter solution provided with FileMaker 13:

Layout canvas for popover button

There is a bit more to configuring a popover. Double click the popover and a Popover Setup HUD appears with the following features:

Popover button setup

  • Calculated title bar for the popover
  • Check box to toggle display of title bar
  • Selection of one of four preferred “directions” to display the popover. Note that a popover will display in a different direction if required to by the window size.
  • On Object script triggers

Popover in Action

And here is a screen shot of the Popover Button as used in the Invoices starter solution that comes with FileMaker Go 13:

Popover button on the iPad

Popover buttons are just one of the features that enhance the user experience in FileMaker 13.  We are also looking forward to using Slide Controls (for iOS swipe gestures), iOS Keyboards for FileMaker Go data entry, and FileMaker Go native barcode scanning.

Filed Under: Layout Design Tagged With: FileMaker 13, Layout objects

FileMaker 13 Field Picker

December 3, 2013 by Anders Monsen Leave a Comment

Field picker in FileMaker 13

Field picker in FileMaker 13

FileMaker 13 introduces a new option in layout mode, which both enhances the design process and also speeds up schema changes. All this happens via the new Field Picker, a heads-up display into the fields for the current active window.

By default, when you create a new database in FileMaker 13, you now will be taken to layout mode with an empty Field Picker ready to create new fields (figure 1). This replaces the previous scenario where you were taken to table view in order to create and manage fields. The default behavior can be changed in Preferences to use Manage Database dialog to create files, but this new Field Picker actually makes it worthwhile to keep the default behavior. Or, you can select the Field Picker from the tool bar (figure 2)

Unlike the Inspector, only one instance of the Field Picker window can be opened. If you have multiple FileMaker windows open, with layouts based on different table occurrences, when you switch windows the Field Picker will update to show the fields available to the active window. You cannot drag fields to inactive windows, so there’s no chance of dragging fields to the wrong layout. Fields can be filtered by name, which is a good reason for consistent field naming.

Filtering by field name

Although you have virtually all the field options that you need, you can launch the Manage Database from the picker window. This makes the picker inactive until you close Manage Database.

It Makes A Big Difference

So much can now be accomplished in the Field Picker, that this becomes one of the coolest developer tools in the new version. Not only can you add new fields, select field options (figure 4), and change the sort order for fields, but you can drag and drop selected fields directly onto a layout. Plus, you can determine whether you want labels, and if you want these to the left or above the fields.

No more double-clicking on fields to add a label if the Specify Field dialog didn’t have this checked. You can also position fields vertically or horizontally when you drag them onto the layout. In short, you can tuck this picker to the side and work merrily away on the layout without having to bring up Manage Database unless you need to change something in the Relationships Graph or create a new table.

Field Options menu

The only puzzling aspect to the new field picker is that Filemaker, Inc. did not refresh the design of the Inspector palette (figure 5). The look and feel of the two now seems to clash, with the red/yellow/green buttons for the Inspector and its light gray color, and the simple X for the Field Picker and with a much darker (yet somewhat transparent) shading.

For developers and users, this new field picker once again improves FileMaker’s Rapid Application Development view of the database world.

Filed Under: Layout Design Tagged With: FileMaker 13, Layout objects

Barcode Scanning in FileMaker 13

December 3, 2013 by Anders Monsen 22 Comments

iPhone scanning barcode

A few months ago I wrote a series of articles (Part 1, Part 2, and Part 3) about barcode scanning in FileMaker Go 12. With the release of FileMaker 13, barcode scanning is now a native feature. There is no longer any need for the FileMaker Pro URL protocol and extra iOS applications.

In FileMaker 13, there is a new “Insert from Device” script step. The action is simple. Select the target field, a container, and from which device you want to insert (music library, photo library, camera, video camera, microphone, and signature).

Insert From Device script step

Once you insert the barcode, you can get information about the barcode using the GetAsText( ) and GetContainerAttribute( ) functions. The former gets only the contents; the latter gets the contents and type of barcode.

There are currently 16 supported barcode types including QR Codes.

Barcode types in FileMaker`

With barcode scanning now natively supported in FileMaker 13, there are more reasons to use FileMaker Go for inventory tracking and management.

Filed Under: Barcodes Tagged With: FileMaker 13, FileMaker Go, Insert From Device

FileMaker Go in the Wild

October 28, 2013 by Darren Burgess 1 Comment

iPads in a charging station

This just in: Our intrepid team of MightyData mobile iPad solution hunters has successfully observed a FileMaker Go mobile database grazing among the sports apparel production machines of long-time MightyData customer and unparalleled sports apparel manufacturer, Lettermen Sports. Our camera traps were ideally placed to observe a spectacular herd of no less than 18 iPads roaming the shop floor, stationed at embroidering machines, screen printing presses and collecting data at multiple work stations.

iPads in a charging station

The behavior of this mobile solution is simply astounding. The native indigenous employees were observed interacting with the beasts, using them to clock in and out of dozens of individual garments of sports apparel orders.  Data was observed streaming to the FileMaker Server, where tribal leader Amy Schumacher was observed running a report summarizing the profitability of individual orders, machines, departments and employees. Rumor has it that this comprehensive and dynamic report is run from a single FileMaker layout and will provide Lettermen with comprehensive productivity and profitability metrics heretofore impossible to obtain.

Embroidery machine with iPad terminal

Customer Feedback

Despite the risks associated with close proximity to the wildly thrashing embroidery machines, we were able to get a brief interview with Schumacher and her chief Production Floor Game Reserve Guide, Eric Milner.  According to Schumacher:

Wow. We are all just so excited to start using this. Well, except for the folks that are afraid of the iPads – they’re not so excited. But everyone else can’t wait to begin working and interacting with this spectacular population of mobile devices and its accompanying FileMaker Go application!

Mr Milner added:

Hey Man. This new mobile beast thing is awesome. But there seems to be a small infestation of software bugs inhabiting the FileMaker Go app-beast. Like it seems that the first contact login procedure for accessing the database is all goofy. The indigenous employees can’t see their orders on the iPad.

Hard Work Pays Off

Emboldened by the excitement of the safari guides at Lettermen, seasoned programmer and MightyData’s Maestro of Metamorphosis, Darren Burgess, was seen in the early dawn hours rapidly eliminating over 10 of these bugs. Preliminary reports from the production reserve have shown that the natives have embraced their new relationship with the wild iPads, helping them to create nearly 300 time clock records in just 2 days.

The MightyData team, in partnership with the Lettermen safari leaders, is excited to see the results of this spectacular FileMaker Go Mobile Application ecosystem. The result of months of planning, preparation and development, this new mobile application promises to deliver high-value results in a dynamic and busy manufacturing environment. Lettermen is looking forward to coming to a dramatically new understanding of its production costs and profits.

Thank you Eric, Amy and Lettermen Sports for embracing new technology in such a creative way, and trusting MightyData to deliver.  Great database software comes from partnership with customers committed to the challenging process of planning, designing and developing solutions. Now, that is what is really spectacular.

Filed Under: MightyData Culture Tagged With: Case study, FileMaker Go, Productivity

  • 1
  • 2
  • 3
  • …
  • 14
  • Next Page »

Let’s get started on your project.

It will be more fun than you think.

Get in Touch

  • Company
  • Services
  • Results
  • Blog

Copyright © 2022 · Parallax Pro Theme on Genesis Framework · WordPress · Log in