Day 1: Course Introduction

This video focuses or terminology, basic product overview and positions.  What is Pro, Go, WebDirect.   Other questions addressed:

I last used FileMaker 15 - what is Claris? Didn’t the company used to be FileMaker Inc?  Is FileMaker still a thing?

I purchased FileMaker from you, but you shipped me software that is 4 years old.

I wrote my company’s database in Access and I want to leave. How do I convince Management to get on board with FileMaker?

How much does FileMaker cost? Should I boy it as a one-time fee or a subscription?

Can I put PDFs/Documents/Videos into FileMaker?

Can I search those PDFs and Documents while they are in FileMaker?

Does Claris see the information I put into my database?

I have complicated legal documents I need to be secure. Is FileMaker safe?

Can I run a FileMaker server on my desktop machine/laptop?

Are there coding/naming conventions for FileMaker?

I’m not a coder. Can I really learn to use FileMaker? 

Day 2: The Basics

User Basics.  Navigating Layouts.  Navigating records.  Layout Mode, Browse Mode, performing finds & sorts.  Form Views, List Views and Table Views.   Status toolbars in browse mode or Find Mode.

List Views, and associated layout parts.   Navigation Header is for display only and not printing.

Status Toolbar is at the top of the layout, and be turned ON or OFF.

FileMaker can provide Low Code experience, but it can expand to be “Pro Code.” 

Day 3: Field Types

For this stream, we recap basic aspects of FileMaker and also discuss the different kinds of Fields in FileMaker. Text, number, date, timestamp, and container fields. 

Quick recap
Richard led a training session on Filemaker, discussing its layout, structure, and functionalities, as well as the importance of understanding business processes and data modeling. He also addressed issues related to layout and appearance changes, the concept of repeating fields, and the generation of serial numbers. Lastly, he discussed the FileMaker Developer Subscription, the importance of backwards compatibility, and encouraged attendees to ask questions and seek professional help when needed.

Next steps
Margaret to make a note about conditional formatting on objects for future discussion.
Margaret to research where control styles are covered in the curriculum.
Richard and Margaret to cover control styles and basics of security in tomorrow's session.
Richard to follow up on the question about customizing sort order for dropdown lists using data from separate fields.
Richard to cover value lists in an upcoming session.
Margaret to link to Nick Hunter's streams for those interested in more advanced topics.
Attendees with questions about buying FileMaker Developer Subscription in Lithuania to reach out to Claris tech support.
Summary
Filemaker Training and Team Success
Richard led a training session on Filemaker, encouraging participants to ask questions and share their experiences. He emphasized the importance of the team's success and the role of the staff in producing the show. Richard also discussed the upcoming material on Fmtraining TV, the subscription process, and the importance of asking questions. He welcomed new participants from various locations and encouraged them to introduce themselves. Richard also mentioned that Clarice would be available to answer any licensing or other questions. The session concluded with a recap of the previous day's discussion and a preview of the day's agenda.
Custom Map Layout and Structure
Richard discussed the layout and structure of a custom map in Filemaker Pro. He explained that the graphical layout is stored in an Fmp 12 file, along with the data and scripts. He also clarified the different modes of operation, including browse, layout, find, and preview modes. Richard demonstrated how to use the left and right panels to manage fields and objects on the layout, and how to adjust the layering of objects. He also addressed some questions about layout-specific issues and promised to cover types of fields in a later discussion.
Designing for User Screen Sizes
Richard discussed the importance of understanding user screen sizes and resolutions for effective layout design. He suggested that users should determine the standard size their users are using, in terms of pixels, and design accordingly. Richard also mentioned the need for different layouts for various devices, such as laptops, desktops, iPhones, and iPads. He advised users to use the'starting point' layout as a default and to create their own pixel size if needed. Richard also mentioned the availability of 'touch' layouts for devices like iPads. He concluded by encouraging users to ask questions and seek clarification.
Software Layout and Field Entry
Richard discussed issues related to layout and appearance changes in a software. He explained that certain states, such as hover, may not work if the necessary credentials are not met or if the object does not support the state. He also mentioned that some objects may not support every state, and that the software has different functionalities for different devices. Richard also touched on the topic of field entry, suggesting that it can be turned off if a field needs to be on the screen but not editable in browse mode. He concluded by stating that he uses most of the features in the software, but not all of them.
Understanding Business Processes and Filemaker
Richard discussed the importance of understanding business processes to effectively implement them in software. He emphasized the need for developers to have a deep understanding of the business they are working with, likening it to the need for a horse masseuse to understand horse massage. Richard also touched on the concept of data modeling, mentioning that he and Margaret were working on a new module for the helicopter operation. He explained the basics of tables and fields in Filemaker, including the different types of fields and how to create them. He also mentioned the concept of container fields for digital document management. Richard encouraged the team to learn more about these concepts and to ask questions.
Filemaker Field Types and Limitations
Richard discussed the functionalities and limitations of various field types in Filemaker, emphasizing the importance of understanding the distinctions between text, number, and container fields. He explained that a number field can only contain one number, while a text field can hold more data but may impact performance if overloaded. Richard also highlighted the importance of formatting fields to display data accurately, using the example of a dollar amount field. He used analogies to explain the limitations of Filemaker, comparing it to a pickup truck that can handle most tasks but may not be suitable for large-scale data handling. Richard also addressed potential performance issues that could arise from overloading fields with excessive data.
Repeating Fields in FileMaker Limitations
Richard discussed the concept of repeating fields in FileMaker, a tool used for database management. He explained that a repeating field is essentially a field with multiple compartments, similar to a box with multiple levels. Richard highlighted that this feature is old and has design limitations, as it can be challenging to process data from different levels of the same field. He also advised against using the validation feature, suggesting that auto-enter is more useful. Richard further explained that repeating fields are not ideal for separating data into different records, as they are "glued together" and cannot be easily isolated. He concluded by acknowledging that some people still use repeating fields, but it is not a recommended practice.
Security, Server Basics, and Layout Objects
Richard discussed the upcoming topics for the next day's meeting, including security, server basics, and layout objects. He also addressed a question about customizing the sort order in dropdown lists, promising to find more information on this. Richard emphasized the importance of understanding the history and interconnections of the topics being discussed, and encouraged the team to focus on what they need to succeed with their organization. He also mentioned the need to cover control styles and relationships, and the importance of data modeling in understanding the organization's tables. Richard encouraged the team to let go of topics they don't need and to focus on what will make them successful.
FileMaker Serial Number Generation
Richard discussed the generation of serial numbers in FileMaker, a database management system. He explained that for beginners and intermediate developers, it's best to use the auto-enter feature for serial numbers, as it's easier to manage relationships. He also mentioned that advanced developers might use a different method involving a random string, which is less likely to repeat. Richard also touched on the importance of unique identification for each record in a database. He suggested that for those needing advanced developer assistance, they could reach out to Nick Hunter, a professional developer with experience in complex projects. Richard also briefly discussed the history of FileMaker and the challenges of maintaining compatibility with older versions of the software.
FileMaker Developer Subscription and Support
Richard discussed the FileMaker Developer Subscription, which includes FileMaker Pro for Mac and Windows, and a copy of FileMaker Server. He mentioned that it can be installed on Mac, Windows, Linux, or an Amazon EC2 server. Richard also addressed a question about purchasing the subscription in Lithuania, suggesting that the person should reach out to Clarice tech support for assistance. He acknowledged the importance of backwards compatibility and the large developer community for FileMaker. Richard also encouraged attendees to ask questions and reach out to Nick Hunter for professional help.

Day 4: Security Basics and Server

Basic of Security.  Internal Accounts, privilege sets, Roles, Extended Privileges.  How to upload a database file to a FileMaker Server.  FMS vs. Cloud.   Building a launcher file for user distribution. (01:08:26)

Day 5: Layout Objects, Day 1

There are a variety of objects that can be placed on a layout. Everything from fields, to rectangles, boxes, lines, buttons, popovers, and webviewers. For part one we cover everything except the objects related to value lists. 

Day 6: Layout Objects, Day 2

Static and Dynamic Value Lists. The uses of different Controls ( Drop Down Lists, Pop Up Menus, Radio Buttons, and Check Boxes) 

Day 7: Finds and Sorts

We cover how to do Finds in FileMaker manually, and a brief discussion about sorts. We discuss operators, includes, omits, and multiple finds. 

Day 8: Introduction to Scripts

Scripting Basics.  Script workspace, disabling/enabling code, understanding context.  How script may fail without proper context.   A button can perform a single script step, or can trigger an entire script.  Conversation about Merge Fields.  Conversation about Plugins.  If Then Script Steps as opposed to If Function and Case functions. 

Day 9: Relationship Introduction

An introduction to Relationships in FileMaker. This includes a break down of the training plan, Relationship Basics, Work Flow, Tables, Fields, and One to Many Relationships. We end the conversation with a brief conversation on the next topic, Conceptual Data Modeling. 

Day 10: Conceptual Data Modeling and Relationship Graph Overview

The term “data modeling” is a fancy word referring to how developers document the tables, fields, and relationships that accurately represent the business or organization. Conceptual data models are sketched out during the planning stages of building a FileMaker app.  Conceptual data models provide a summary-level perspective, omitting finer details in favor of a more readily digestible format. 

Sample File: https://bit.ly/Margs_Adventures_60
(admin / no password)

Day 11: Focused Conversation on Data Modeling

This is a bonus video for those who need the extra help with Data Modeling. The term “data modeling” is a fancy word referring to how developers document the tables, fields, and relationships that accurately represent the business or organization. Every business is different and how you data model will depend on each specific business. 

Day 12: Lookups

As we wrap up the conversation on conceptual data modeling, we take a moment to discuss Lookups. The term “data modeling” is a fancy word referring to how developers document the tables, fields, and relationships that accurately represent the business or organization. Conceptual data models are sketched out during the planning stages of building a FileMaker app.  Conceptual data models provide a summary-level perspective, omitting finer details in favor of a more readily digestible format. 

Day 13: Organizing the Relationship Graph, Anchor Buoy

Critical video for Beginners and Intermediate developers.  Anchor Buoy is process/technique to help you create  clean and simple relational graph.  This technique is absolutely essential to ensure fast performance from your FileMaker database, while also making the relational diagram easy to troubleshoot. (01:03:12)

Day 14: Introduction to Portals

A portal is a layout object. When you place the portal into a layout, it is will display information from a related table… in rows - with one row in a portal representing one related record.   A portal can be configured to display one or more fields from the related table. 

Day 15: Portal Filtering - Intermediate Skillset

A portal is driven by the underlying relationship.   Therefore, logically you can limit the records being displayed by manipulation of the underlying relationship. 

Day 16: Portal Automation - Scripting Portal Control

Scripting automation to satisfy the needs of the end users is an essential skill for the developer.   However, the developer will find  that writing a script that DIRECTLY MANIPULATES a portal object on the layout, is difficult, time consuming, and in the end, fairly fragile.

Writing scripts can be simplified for the beginner or intermediate developers if that developer is able verbally articulate each individual step, as if they were talking to a users via a phone conversation.

For success in automating interaction with a portal, the developer needs to largely control the contents of the portal by popping a new window and directly manipulating the records, either in a form view or a list view, and not trying to manipulate the records directly through the portal object itself. 

Day 17: Many to Many Relationships - Basics

Many to Many relationships are hard to understand in an educational environment. Whatever you break it down to business issues, that these are very easy to understand. Developers tend to use the word join table, when they‘re unable to describe the actual underlying business process. 

Sample File: https://bit.ly/Classes_Many_to_Many
(admin / 1234)

Day 18: Many to Many Relationships - “Travel Packages”

Many to Many relationships are hard to understand in an educational environment. This is one of two more more scenarios and examples we included to help.

Day 19: Many to Many Relationships - “Cora and the Dinosaurs”

Many to Many relationships are hard to understand in an educational environment. This is one of two more more scenarios and examples we included to help.

Day 20: Calc Field Storage, Indexing and Performance

We cover the options for indexing and storing your data to achieve the highest level of performance possible.  The yellow Post-it Notes Diagram Video. 

Day 21: Calculations in FileMaker

•Stored/Unstored/Cached Calcs
•Indexing/Non-Indexed Fields

Day 22: Shaking the Dependency FileMaker Tree

Understanding Calculations in the Claris FileMaker platform and when they fire.  Featuring presenter Darren Terry.

Day 23: Variables & Preference Tables

There are four common situations where we want to collect and interact with data...as part of a script, and using “normal” fields is not a good fit.

Local Variables:   Developer needs to track some data ONLY while a script is running.  Once the script ends... we don’t need that data, so it can be dumped out of memory. Example:  tracking which record a script is acting on.   When the script is done, we don’t care about this anymore.

Global Variables:  Developer needs to track some data ONLY while a user session is running.   When the user logs out of a FileMaker File, we can dump this data.  Example:  What kind of computer device they are using while logged into a session. 

Preference Table:   Developer need to track preference setting that is shared with all users of the FileMaker solution.   What is the preferred phone number customer should call to reach out sales department?   That might be useful for all users, and should be preserved.

Global Fields:  Developer need to allow a user to enter data into the database, but we want the user to be able to cancel out, without saving the data.   Combine global fields, with a scripted process. 

Day 24: Document Management

Today we discuss the basics of containers and document management. What is the difference between standard and interactive containers. We will learn about storage options, security, validation, and optimization. We will also go over how to capture signatures, resize images within a container, and capture thumbnails. We will also go over techniques on importing, exporting, capturing signatures in Go, resizing images, and capturing thumbnails.

Day 25: Most Common Script Uses

There’s a variety of basic script processes that are almost universal between databases. For this stream we’re here to talk about those!

Day 26: Navigational Scripts, Device Screen Size

Design Considerations for Phones, Tablets, and desktop computers.  Mouse or Touch, regulates the size of the on-screen objects.  Also discussing layout objects that can help manage screen real estate, Slide Control Tab Control, and Pop over Windows.

Day 27: Print Layouts - Introduction

Printing to paper or PDF takes a bit of fore thought.  Think about having print specific layouts, that are different than data entry. Printing a PDF is essentially the same as printing, but you will probably want to write a script that saves the PDF to a specific location on your computer.

Day 28: Print Layouts - Scripts for Printing and Saving to PDF

Printing to paper or PDF takes a bit of fore thought.  Think about having print specific layouts, that are different than data entry. Printing a PDF is essentially the same as printing, but you will probably want to write a script that saves the PDF to a specific location on your computer.

Day 29: Print Layouts - Printing Portals Across Page Breaks

Printing to paper or PDF takes a bit of fore thought.  Think about having print specific layouts, that are different than data entry. Printing a PDF is essentially the same as printing, but you will probably want to write a script that saves the PDF to a specific location on your computer.

Day 30: Importing and Exporting Data

Understand the Import and Export processes.  Understand differences between running these manually and via script.  Understand how imports can be saved with a script for future re-use.  Also learn about auto-enter options as records are imported.

Day 31: Bringing It All Together: Build an Automation Script From Scratch Using All Our Previous Taught Skills.

Comprehensive training session on using FileMaker scripts to automate Invoice/PO/Project record duplication in FileMaker.  This training is designed for both beginner and intermediate developers.  We focus on using all the skills we have trained previously:  Including script debugging techniques and troubleshooting methods. Video walks through examples of creating and managing scripts for duplicating invoices, line items, and records between windows, emphasizing proper variable management, error checking, and code commenting. The session concluded with discussions about FileMaker Server processing, web direct performance considerations, and best practices for record management and data transfer between windows.

Day 32: Multi Users and Single Users

Understanding how FileMaker behavior changes after being hosted on a server is important.  Record locking is an important consideration.  Script frequently can lock records, so we’ll explore this issue, along with Error Trapping.   We will also look at how Global fields behave differently.

Day 33: Naming Conventions

Unique, consistent names for scripts, layouts, relationships, and table occurrences are needed to stop developer confusion. Resequencing is inevitable, we discuss how you can make this easier on yourself. There are specific layouts that can’t be renamed without breaking other parts of your database.  Anchor-buoy has very specific naming conventions to make it easier to “read”. 

Day 34: Reports & Subsummaries

Reporting is the last thing that developers typically build in a FileMaker solution.  But report should ideally be documented and planned BEFORE building the FileMaker app.   Summary fields, and Subsummary body parts are essential for MOST reports.

Day 35: Saving Your Data

How exactly is data ‘saved’ in FileMaker? How do you convince your users that the data is saved? 

Day 36: Script Triggers - Part 1

By using any of the 26 script triggers in FileMaker, you can run scripts that are triggered by a host of user actions, including layout and record navigation, rotating a mobile device, entering or exiting a field, and changing modes or views.

As useful as script triggers are, they can add complexity to your apps, and have the potential for undesirable consequences. 

Day 37: Script Triggers & Parameters - Part 2

Communicating with a Script that will run, is running, or has already completed is a critical skill. Script parameters are a way of exchanging data to a script that has just been activated. Script results are text strings that come from scripts that have just completed. 

Day 38: Script Triggers & Parameters - Part 3

Today we talk about parameters, validation, and continuing our discussion on Script Triggers.

Day 39: Hiding Objects in FileMaker

We cover how to hide objects on your layouts, reasons you might need to hide objects, and understanding the sometimes awkward scripting language in hiding objects. 

Day 40: Identifying and Dealing with Duplicate Records

In this video we will be breaking down ,step by step, our own record de-duplication script to help you identify and deal with duplicate records.

Day 41: Charting

Charting in FileMaker can be difficult and complex, but is an oft requested feature. Calvin is here to break the basics of it down for you. 

Sample File: https://bit.ly/Calvin_Chart_60 

Day 42: Emailing

FileMaker Pro has built in script step to send outbound emails. Emails may be sent manually  via script step. The Send Mail script step will send text only email through one of two methods. Emails may be sent via a locally installed email application, or emails may be sent out directly to the internet via SMTP (Simple Mail Transfer Protocol) configuration.

Day 43: WebDirect for Beginners - Overview, Planning & Licensing

WebDirect is how you access FileMaker on a browser, but there are some inherent pitfalls, both designing and using FileMaker for web browsers. 

Day 44: WebDirect for Beginners - Design Basics and Strategies for Performance

WebDirect is how you access FileMaker on a browser, but there are some inherent pitfalls, both designing and using FileMaker for web browsers. 

Day 45: Calendars

Calendars are not native to the FileMaker platform, and as a general rule are not provided by Claris. Calendars can be rendered using Webviewers, and are a tricky, more advanced topic.   We cover the Calendar in FMSP, it’s features, and show you how to move it to a different layout.  

Day 46: Perform Script on Server

Perform Script on Server is a vital, if complicated script step. It allows you to send scripts to the FileMaker server to run. Jonathan Ray is here to break down the details of it for beginners. 

Day 47: Multi-file Solutions

Most modern FileMaker files will be single file solutions. This is traditionally easier to manage, but there are reasons to have multi-file solutions. Different departments will not want to share the same solution.

Day 48: Record Level Security & Layout Level Security

You can add a wide variety of security levels to your FileMaker database. Records and layouts can have restricted access through custom privilege sets. 

Day 49: FileMaker Server Q&A with Jacob Taylor

This video does not cover “Why should I use FileMaker Server.”   This video focuses on basic administrative tasks or capabilities that FileMaker Server Admins should be aware of… including opportunities to improve server performance. 

Understand Capabilities of FMS Web Interface

Understand RAM cache, and that everyone needs to adjust this. This setting is almost ALWAYS wrong after an initial FMS installation.

“Administrator Roles” allows Multiple Departments to manage their own database solutions separately…. while being co-located on the same server. 

Understand the FMS Web Interface Charts.

Be aware that if your FIleMaker License expires, then at some point your FMS will shut down.

Full SSL Certificates should be used.

“Show Extended Privileges” is now a visual capability…awesome for FMS administrators. 

“Back up Schedules” was moved in FMS 21 (2024 release)

Does it matter which SSL vendor you use?

If the server is hosted on FileMaker Cloud, does that include SSL?

Schedules have been consolidated into a single location.

High Level Discussion of OAuth

When I try to set an additional container folder, I always get “path is not valid”
Mac Permissions for fmp12 files

What Mac Mini should I use for an On-Site FileMaker Server?

Disaster Planning and Recovery

How many Backup drivers should I use for an Onsite FMS?

What is Error “HTTP Status 503 Service Unavailable” ?

Installing Java Runtimes.

Day 50: Final Q&A

I am migrating from FileMaker 12, 13, 14, 15, 16, 17, 18 19….. what do I have to be concerned about?

What is the “fmp12” file format?

Why does Claris not build an iPad version that does development? 

Creating Log Entries with a Script running from the FileMaker Server, PSOS.

Sample File: https://bit.ly/audit_logs_BVA 
(admin / 1234)