FileMaker Layout Tips

I do a lot of fiddling with layout designs for a lot of our different FileMaker projects, and there’s a few useful things I’ve learned, mostly by accident or by blundering around. If you don’t already know these, maybe it will save you some time…

Multiple Inspectors

The day I realized I could have multiple inspectors open was a happy day for me. No more jumping from position tab to data tab, then back again for the next field I needed to review. Just pop open another Inspector window so you can have one for one tab and one for another (heck, if you have a really big screen, why not have one for each?!). To open another Inspector, just select “New Inspector” from the View menu.

Sample Data

We recently got feedback from our E-Com customers that some of the fields on new forms we had created were not long enough for their student names, or for the names of responsible staff members. We thought we had made the fields long enough – our fairly long field names appeared with plenty of room – but we had miscalculated. Using the Sample Data option in Layout mode when the fields were filled with long sample names in Browse mode revealed how we needed to rearrange and lengthen these fields. It was so much easier to do with the sample data visible in Layout! It may be found under View > Show > Sample Data.

Hover

I love the hover function introduced in FileMaker Pro v14! Now I can see what any badge is doing for us without having to dig. It includes any relevant script names. Just hover your cursor over the badge and voila. It tells what conditional formatting, what script trigger, what script, you name it.

Resizing Merge Fields

The Position tab of the Inspector allows you to resize merge fields to better fit the data inside rather than the names of fields – this is really great when you have very long field names with very short data and you need to place other elements around it. Select the merge text area and simply change the width of the field. Showing sample data here can help, as well.

~Alanna Clare

FileMaker 15 Released

Today FileMaker Inc. released FileMaker Pro and FileMaker Server 15. This is the first release since they announced a new annual release schedule last year, so presumably we’ll see FileMaker 16 approximately a year from now.

FileMaker 15 has a number of interesting new features. I’ve picked out a few features that seem most useful and highlighted them below.

‘In App’ Software Updates
You no longer have to download an updater to keep FileMaker 15 current. The app will simply prompt you to perform the update similar to the way app updates work on an iPhone.

Script Undo
The script workspace now allows multiple levels of undo and redo. This will make it easier to change your mind and undo the last 5 minutes worth scripting changes.

Security Improvements
A number of areas in FileMaker have been updated to allow you to work more effectively with 3rd party SSL certificates to enhance the security of your applications.

iBeacon Support
A new script step enables FileMaker to access iBeacon information in the nearby bluetooth environment. This could allow your FileMaker app to do all kinds of interesting things based on its proximity to an iBeacon. Examples might include automatically displaying the contents of a container that you are nearby or displaying additional information about a product that you are standing in front of.

Truncate Table
This won’t necessarily be useful to all people, but the new Truncate Table script step will be very useful in some situations. In my brief testing, the 'Delete All Records' script step cleared out a table with 117,000 records in 5 minutes and 10 seconds. The new 'Truncate Table' script step did it in 14 seconds.
~ John Newhoff

VR Hackathon 2016

I recently attended the Virtual Reality (VR) Hackathon 2016 in Seattle. Although I ultimately didn’t work on a very exclusive “VR" hack. I got to meet a lot of interesting people, look at some really cool VR tech, and learned how to hack the Amazon Echo.

The Seattle VR Hackathon 2016 ran the 3rd weekend in April at the University of Washington. It started Friday night and ran until Sunday afternoon.

During the Hackathon Friday night mixer, we formed into groups. The group I joined consisted of three people. After forming the group, we began to decide what we would do for our hack. One of the back-end developers in the group wanted to do something with the Amazon Echo hardware. The other developer and myself wanted to do data visualization in VR. We tossed around several ideas and decided the Amazon Echo, with the use of its AI, named Alexa, would be a great utility to assist users while immersed in VR. Unfortunately, this meant that the data visualization would need to wait. The clouds slowly parted and the plan materialized. We would use Alexa as our personal assistant while in VR.

Because you can become so involved in the VR world with goggles on, you need a connection to the real world in order to do things like order a pizza, call your mom, or text your friends to join you in a game. The idea we had was a utility function that would allow you to send communications to the real world without interrupting game play - to provide you the ability to send your friend a text message and tell him/her to come join you in the game, by simply asking Alexa to do it. Once the plan was set, we parted for the night.

Saturday morning we met up again, and after a primer tutorial by the Amazon team, we confirmed that the Echo would work great for our project. We got started putting the pieces of the puzzle together. In order to accomplish it we would need to use a few different services.

• Amazon Echo for voice interaction. Amazon Echo uses an AI and responds to the name Alexa.
• Amazons AWS Lambda for handling the logic and programmatic responses to our requests. AWS Lambda is a serverless compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
• Twilio for making telephone calls and sending text messages.  Twilio allows software developers to programmatically make and receive phone calls and send and receive text messages using its web service APIs.

By creating a set of what is termed as "Alexa skills," we could trigger programmed events to be passed using speech recognition from Alexa and get scripted interaction with people in the real world. The functions called by "Alexa skills" were handled by the AWS service Lambda. Using Lambda, we could write functions in node.js, python, or java. The functions would make web services calls to Twilio. Using the Twilio API, we were able to write scripts to make the telephone call or send a text message. Once the person received the phone call and text, the Amazon Echo would respond back to the user in a nice voice with a programmatic response like "message sent."

By the end of Saturday we had a working prototype where a user could say out loud “Alexa, call John!” and immediately the user would receive a text message confirming the call had been sent. Alexa would then respond “Done!” and the person “John” would receive a telephone call, on his cell phone, from a Twilio robot telling him the words we had programmed it to say. With a little knuckle grease, some refreshers to node.js, a few facepalms, the pieces of the puzzle weren’t that difficult to put together.

The last day of the Hackathon came and we presented to the judges and other hackers. As with many of the hacker events, there were a bunch of attendees, which made 24+ teams and some really good hacks. Our hack only loosely fit in with two of the six categories, and we didn’t win in either of those categories. Although we didn’t win any prizes, we had a great time and we learned some valuable skills that I will definitely use on other projects. All that said, it was a lot of fun and I would do it again.
~Xandon Frogget