Why Your Processes Break Every Time Volume Increases

Many business processes work perfectly, until they don’t.

At low volumes, manual steps, spreadsheets, and loosely connected systems feel manageable. Orders get processed, reports get built, and workflows move forward. But as volume increases – more customers, more transactions, more production – those same processes begin to break down.

The issue isn’t the team. It’s the system those processes rely on.

Designed for Today, Not for Scale

Most processes are built to handle current demand, not future growth. Early on, teams optimize for speed and flexibility:

  • Manual approvals instead of automated workflows

  • Spreadsheet tracking instead of structured systems

  • One-off reports instead of real-time dashboards

  • Human coordination instead of system-driven logic

These approaches work… until volume increases.

What Happens as Volume Grows

As activity scales, small inefficiencies compound:

  • Manual steps multiply: More data means more entry, validation, and reconciliation

  • Errors increase: Higher volume leads to more opportunities for mistakes

  • Delays grow: Processes that once took minutes now take hours or days

  • Visibility decreases: It becomes harder to track status across workflows

  • Teams feel overwhelmed: Workload grows faster than capacity

What once felt efficient becomes a bottleneck.

Why Adding People Isn’t Enough

A common response to increased volume is to add headcount. While this can help in the short term, it doesn’t address the root issue.

If the process itself is inefficient, adding more people often introduces:

  • More handoffs

  • More coordination overhead

  • More opportunities for miscommunication

Without system improvements, complexity increases alongside volume.

Building Processes That Scale

This is where Claris FileMaker enables a different approach. Instead of relying on manual workflows, organizations can:

  • Automate repetitive tasks

  • Centralize data across operations

  • Implement real-time tracking and status updates

  • Apply validation rules at scale

  • Create dashboards that reflect current conditions instantly

With the right infrastructure, processes don’t just survive increased volume, they perform better because of it.

Why This Matters

Growth should improve efficiency, not expose weaknesses. Building processes that scale ensures that increased demand leads to better performance, not operational strain.

If your processes break every time volume increases, it’s a sign they were never designed to scale. Upgrading your systems allows your operations to grow alongside your business without the friction.

Interested in building scalable workflows with Claris FileMaker? Reach out to Kyo Logic here.


When Small Workarounds Become Permanent Infrastructure

Most operational workarounds begin with good intentions.

A quick spreadsheet to track something new. A manual report to fill a gap. A copied dataset to bridge two systems. Each solution is meant to be temporary—a way to keep things moving and addresses a current need.

And over time, those temporary fixes tend to stick. What started as a short-term solution slowly becomes part of the day-to-day workflow, or a broken workflow. Eventually, those workarounds aren’t just supporting operations, they are the infrastructure.

How Temporary Fixes Become Permanent

Workarounds typically follow a familiar path:

  • A gap appears in an existing system

  • A quick solution is created outside the system

  • The solution works, so it’s reused

  • More processes begin to rely on it

  • Additional layers are added to support new needs

 

Before long, multiple workflows depend on tools that were never designed to scale.

The Risks of “Unofficial” Infrastructure

When workarounds become permanent, several issues emerge:

  • Lack of visibility: Critical processes live outside core systems

  • Inconsistent data: Multiple versions of the same information

  • Manual effort: Repetitive tasks required to maintain workflows

  • Limited control: Few permissions, validations, or audit trails

  • Scalability constraints: Processes struggle to handle growth

Because these systems evolved organically, they’re rarely optimized for efficiency or reliability.

Why It’s Easy to Miss

The transition from temporary to permanent happens gradually. Each step makes sense in isolation. Teams adapt, processes evolve, and the system continues to function, only with increasing complexity.

By the time issues become noticeable, the workaround is deeply embedded in operations.

Replacing Workarounds with Scalable Systems

A platform like Claris FileMaker allows organizations to take those fragmented processes and rebuild them into structured workflows. Instead of relying on disconnected tools, teams can:

  • Centralize data and processes

  • Automate manual steps

  • Apply validation and permissions

  • Create real-time visibility across workflows

  • Adapt systems as new requirements emerge

The goal isn’t to eliminate flexibility, it’s to support it within a scalable framework.

Why This Matters

Workarounds are useful in the moment, but they’re not designed for long-term growth. When they become permanent infrastructure, they introduce risk and constrain progress.

Replacing them with purpose-built systems helps organizations operate more efficiently and scale with confidence.

Temporary fixes have a way of becoming permanent. Recognizing when that shift has happened is the first step toward building stronger, more reliable operations.

Interested in replacing workarounds with scalable systems built in Claris FileMaker? Reach out to Kyo Logic here.

 

 

When Your Data Lives in Five Different Places

Modern businesses rely on multiple tools: CRMs, accounting platforms, spreadsheets, project trackers, and more. Each system serves a purpose. But when data is spread across too many places, the real challenge becomes alignment. And, unaligned systems become inefficient.

When your data lives in five different systems, your team spends more time chasing information than using it.

How Fragmentation Happens

Data fragmentation usually builds gradually:

  • A CRM for customer relationships

  • Accounting software for financials

  • Spreadsheets for custom tracking

  • Project tools for operations

  • Marketing platforms for campaign performance

Each tool solves a specific need. But without integration, data becomes siloed.

The Cost of Disconnected Data

When systems don’t communicate, teams face ongoing friction:

  • Conflicting numbers: Reports don’t match across platforms

  • Manual reconciliation: Time spent aligning datasets

  • Delayed insights: Decisions wait on data consolidation

  • Duplicate entry: The same data entered in multiple places

  • Limited visibility: No single source of truth

Over time, this creates operational drag that slows execution and increases frustration.

Why “More Tools” Doesn’t Solve the Problem

Adding more tools rarely fixes fragmentation. In many cases, it makes it worse. Each new system introduces another data source and another integration gap.

The issue isn’t the number of tools. It’s the lack of connection between them.

Creating a Single Source of Truth

This is where Claris FileMaker plays a critical role. Instead of replacing every system, FileMaker can act as a central hub that:

  • Integrates data from multiple platforms

  • Synchronizes updates across systems

  • Automates data flows between tools

  • Provides unified dashboards and reporting

  • Eliminates duplicate entry and reconciliation

With a centralized layer, teams gain clarity without sacrificing flexibility.

Why This Matters

When data is unified, organizations can:

  • Make faster, more confident decisions

  • Reduce manual work

  • Improve reporting accuracy

  • Align teams around consistent metrics

  • Scale operations more efficiently

The difference isn’t just convenience, it’s performance.

When your data lives in multiple disconnected systems, the cost shows up in time, accuracy, and decision-making. Creating a unified data layer allows teams to move faster and operate with confidence.

Interested in aligning your data with Claris FileMaker? Reach out to Kyo Logic here.


When “Just One More Spreadsheet” Becomes a Bottleneck

Most spreadsheet sprawl doesn’t start as a bad decision. It starts as a practical one.

A team needs to track something new. A report doesn’t quite fit the system. A one-off process pops up. So someone creates just one more spreadsheet to handle the edge case. It works… at first.

Over time, though, those quick fixes add up. What began as a flexible workaround slowly becomes a bottleneck that limits scale, creates risk, and makes it harder for teams to move quickly.

How Spreadsheet Sprawl Sneaks In

Spreadsheets often fill gaps where systems fall short. Common triggers include:

  • Tracking exceptions that don’t fit an existing workflow

  • Managing temporary processes that become permanent

  • Reconciling data between disconnected tools

  • Creating “helper” sheets for reporting or approvals

Each spreadsheet solves a real problem in the moment. But as more are added, teams lose visibility into which file is the source of truth (and whether the data is even current).

The Hidden Cost of “Good Enough”

As spreadsheet usage grows, so do the risks:

  • Version confusion: Multiple copies with conflicting numbers

  • Manual errors: Broken formulas or accidental overwrites

  • Slower workflows: Time spent updating, reconciling, and validating data

  • Limited access control: Anyone with the file can often edit critical values

  • No audit trail: Changes happen without clear accountability

Eventually, teams spend more time managing spreadsheets than solving the problems they were meant to address.

Where Throughput Starts to Break Down

Spreadsheets don’t fail loudly, they fail gradually. As volume increases, teams hit natural limits:

  • Processes rely on one person who “knows the spreadsheet”

  • Reporting cycles stretch longer each month

  • Edge cases require even more spreadsheets

  • Leadership hesitates to trust the numbers

At that point, the issue isn’t the data itself—it’s the infrastructure supporting it.

A Better Way to Handle Edge Cases

This is where Claris FileMaker often comes into the picture. Instead of creating new spreadsheets for every exception, teams can use FileMaker to:

  • Extend existing workflows without breaking them

  • Centralize data while supporting flexible logic

  • Automate edge-case handling with scripts and rules

  • Enforce validation and permissions

  • Maintain a clear audit trail

Even better, FileMaker allows teams to start small (replacing the most painful spreadsheets first) without needing to overhaul everything at once.

Teams rarely notice when spreadsheets become a bottleneck because the change is gradual. But over time, throughput slows, errors increase, and decision-making suffers.

Replacing spreadsheet sprawl with a purpose-built system doesn’t just improve efficiency, it restores confidence in the data and frees teams to focus on higher-value work.

“Just one more spreadsheet” is often a reasonable short-term fix, but it’s rarely a long-term solution. When workarounds start capping throughput and increasing risk, it’s a sign that your processes have outgrown spreadsheets.

Interested in replacing spreadsheet sprawl with a scalable solution built in Claris FileMaker? Reach out to Kyo Logic here.



When Manual Processes Quietly Limit Growth

Not all growth limitations are obvious. Some don’t show up in dashboards or financial reports. They don’t trigger alarms. Instead, they live inside small, repetitive manual tasks that quietly cap throughput.

Over time, these tasks accumulate. Each one seems manageable on its own. Together, they create invisible ceilings that slow expansion.

What Quiet Bottlenecks Look Like

Manual processes often hide in places like:

  • Re-keying data between systems

  • Manually reconciling reports

  • Email-based approval chains

  • Spreadsheet-based tracking

  • Status updates handled through chat

  • Data cleanup before every reporting cycle

These tasks rarely appear strategic, but they consume meaningful time.

The Throughput Ceiling Effect

As demand increases—more customers, more transactions, more data—manual steps scale linearly with workload.

That means:

  • More hires are needed just to maintain pace

  • Errors increase with volume

  • Reporting cycles stretch longer

  • Teams feel constantly busy but not necessarily productive

Leadership may attribute slowdowns to staffing or market conditions, when the root cause is process design.

Why These Bottlenecks Go Unnoticed

Manual limitations often stay invisible because:

  • They are distributed across departments

  • No single task looks overwhelming

  • Workarounds become normalized

  • Teams compensate quietly

By the time leadership recognizes the problem, operational drag has already slowed momentum.

Turning Manual Work into Automated Flow

This is where Claris FileMaker can transform operations. Instead of layering people onto manual processes, organizations can:

  • Automate repetitive data transfers

  • Replace spreadsheet tracking with structured workflows

  • Enforce validation rules automatically

  • Build dashboards that update in real time

  • Reduce reliance on email-based approvals

When manual steps are automated, throughput increases without adding headcount.

Why This Matters

Growth should create leverage—not complexity. Identifying and eliminating low-visibility manual tasks ensures that scaling doesn’t require proportional increases in effort.

The difference between sustainable growth and operational drag often comes down to infrastructure.

Manual processes rarely announce themselves as growth constraints. But over time, they cap throughput and increase risk. Replacing them with automated, structured systems unlocks capacity that may already exist inside your team.

Interested in identifying and eliminating hidden manual bottlenecks with Claris FileMaker? Reach out to Kyo Logic here.

Automate EOY Tax Document Preparation with FileMaker

Year-end tax preparation often requires pulling data from multiple systems, reconciling totals, and manually generating reports. This process is time-consuming and prone to errors—especially for organizations managing large vendor lists or complex payroll structures. With Claris FileMaker, businesses can automate tax document preparation and generate accurate, audit-ready outputs with minimal manual effort.

Centralize Tax-Relevant Data

FileMaker can consolidate tax-related information, such as:

  • Vendor payments
  • Contractor compensation
  • Payroll summaries
  • Expense reimbursements
  • Withholding data

By storing this information in a structured database, FileMaker ensures totals are accurate and consistent across reports.

Automated 1099 and Vendor Summaries

Custom FileMaker workflows can automatically calculate:

  • Total annual payments by vendor
  • 1099-eligible compensation
  • Threshold checks
  • Category-based summaries

This allows teams to generate 1099 summaries or export-ready datasets without manually filtering spreadsheets.

Generate Tax-Ready Reports and Exports

FileMaker can produce:

  • Internal review and approval reports (Move to top bullet)
  • CSV or Excel exports for tax software
  • Vendor-specific breakdowns

Because reports are generated from live data, updates are applied instantly when corrections are made.

Integrate with QuickBooks

Beyond generating essential in-house reports, FileMaker excels at integrating with external accounting platforms, most notably QuickBooks. This connection is critical for streamlining the End-of-Year tax preparation process.

  • Exports structured vendor/expense data in QuickBooks-compatible formats.
  • Reconciles internal data with QuickBooks before export, flagging discrepancies.
  • Maintains a complete audit trail linking internal processes to QuickBooks financial data

This integration ensures accurate, timely, and fully documented data for tax professionals, smoothing the transition to official tax filing.

 

Why It Matters

Automating tax preparation with FileMaker helps organizations:

  • Reduce manual errors
  • Save time during year-end close
  • Improve compliance accuracy
  • Maintain clear audit trails
  • Respond faster to accountant or auditor requests

Tax prep becomes predictable and repeatable instead of stressful and reactive. Claris FileMaker can send and receive data directly to accounting packages like QuickBooks Online, simplifying the preparation process.

Claris FileMaker simplifies year-end tax document preparation by automating calculations, consolidating data, and generating tax-ready reports. With the right workflows in place, organizations can approach tax season with confidence and control.

Want to automate tax reporting and documentation with Claris FileMaker?
Reach out to Kyo Logic here.

Year-End Budgeting & Expense Tracking in FileMaker

Year-end budgeting often exposes the limitations of spreadsheets. Version conflicts, manual updates, and disconnected expense data make it difficult for teams to collaborate or trust the numbers. With Claris FileMaker, organizations can replace spreadsheets with a centralized budgeting and expense-tracking system that updates in real time and stays synchronized across teams.

Centralize Budget and Expense Data

FileMaker allows finance teams to consolidate all budgeting and expense data into a single system, including:

  • Department budgets
  • Actual expenses
  • Forecasted spend
  • Vendor costs
  • Project or initiative allocations

Data can be imported or integrated from accounting systems, purchasing tools, or expense platforms, creating a single source of truth for year-end planning.

Real-Time Budget Visibility Across Teams

Instead of waiting for monthly spreadsheet updates, FileMaker dashboards show live budget performance:

  • Budget vs. actual spend
  • Remaining budget by department
  • Overages and variances
  • Year-over-year comparisons

Because FileMaker updates instantly as expenses are logged or approved, stakeholders always see the most current numbers. A powerful graphing engine shows trends at a glance.

Collaborative, Role-Based Access

FileMaker supports role-based access, allowing:

  • Department heads to submit or review expenses
  • Finance teams to manage approvals and adjustments
  • Executives to view high-level summaries

This eliminates email chains and spreadsheet handoffs, while maintaining control and accountability.

Why It Matters

Replacing spreadsheets with FileMaker helps organizations:

  • Improve budget accuracy
  • Reduce manual reconciliation
  • Speed up year-end close
  • Increase transparency across teams
  • Prepare more reliable budgets for the new year

Budgeting becomes a living process instead of a static, once-a-year exercise.

Claris FileMaker gives organizations a smarter way to manage year-end budgeting and expense tracking. With real-time data, collaborative workflows, and centralized reporting, teams can plan confidently—and enter the new year with clarity.

Interested in replacing spreadsheets with a custom budgeting system in Claris FileMaker? Reach out to Kyo Logic here.

Calendar Invite Creator: send real calendar invites straight from FileMaker

Free FileMaker add-on

Calendar Invite Creator: send real calendar invites straight from FileMaker

Turn a meeting on a FileMaker record into a standard .ics invite your attendees can accept in Outlook, Apple Calendar, or Google Calendar.

Yes, FileMaker can send real calendar invites. Using native script steps available since FileMaker Pro 18, it can build a standard iCalendar (.ics) file and attach it to an email, and most modern calendar apps treat that email as a meeting invitation with accept and decline buttons. The free Calendar Invite Creator add-on gives you a working version you can open and adapt.

Here is the moment it exists for. A site inspection is booked in FileMaker for Thursday at 9 a.m. The inspector hears about it in a forwarded email, types it into his calendar by hand, and gets the time zone wrong. The customer waits on site for an hour. The inspection record had every detail right the whole time. It just had no way to put the meeting on anyone’s calendar.

How do calendar invites work from FileMaker?

Calendar invitations travel as .ics files that follow the iCalendar standard (RFC 5545). When an .ics file is attached to an email, calendar apps such as Outlook, Apple Calendar, and Google Calendar detect it and offer to accept, decline, or tentatively accept the event.

From FileMaker’s side, that is three jobs: assemble the meeting details as iCalendar text, write that text to an .ics file, and attach the file to an email. Because .ics files are plain text, FileMaker’s Data File script steps cover the middle step with nothing extra installed.

What the add-on does out of the box

Open the included KYO_CalendarInviteCreator_Addon.fmp12 file and click Create Add-on to save it as an add-on you can install in your own app. Then enter the meeting details, add attendees and an organizer, and send. The flow behind that button looks like this:

A user schedules a meeting on a FileMaker record

↓

The add-on assembles the start, end, location, organizer, and attendees as iCalendar text

↓

Create Data File, Open Data File, and Write to Data File save it as an .ics file

↓

FileMaker emails the file as an attachment through SMTP or the default mail client

↓

Each attendee sees a standard invite they can accept or decline

Here is an example of the iCalendar text the add-on produces:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Meetings_Manager//FileMaker Pro//EN
METHOD:REQUEST
BEGIN:VEVENT
SUMMARY:FileMaker Pro Meeting Invite Creation Demo
UID:4821265E-F188-4A3B-9B47-6B62023885B8@fakemeetingscompany.com
DTSTAMP:20260128T185213Z
DTSTART:20260128T233000Z
DTEND:20260129T000000Z
LOCATION:Online Only
ORGANIZER;CN=Kyo Logic:mailto:kyoLogic@testEmail.test
ATTENDEE;CN=Test Person:mailto:testEmail@testEmail.test
SEQUENCE:2
END:VEVENT
END:VCALENDAR

Every line maps to data that usually already lives in FileMaker: the start and end times, the attendees, and the organizer.

The iCalendar rules that trip people up

The approach is simple. The details are where a proof of concept turns into something you can trust in production.

  • Line length. RFC 5545 limits each line to 75 octets. Longer titles and descriptions have to be folded onto continuation lines that start with a space or tab. Folding errors can make an invite get ignored without any error.
  • Time zones. Times are usually written in UTC with a trailing Z. Get the conversion wrong and the meeting shows up at the wrong hour for some recipients.
  • METHOD. METHOD:REQUEST asks recipients to respond. Without it, some apps simply add the event to the calendar.
  • UID and SEQUENCE. Keep the same UID for the life of an event and increase SEQUENCE when it changes. A missing or duplicated UID creates duplicate events instead of updates.

Calendar apps also behave differently, especially desktop versus web calendars. Test with more than one client and with real email addresses before you roll it out.

Where invites from FileMaker earn their keep

  • Project and client meetings: every participant gets the same details, tied to the project record.
  • Inspections and site visits: field staff get the invite the moment the inspection is assigned.
  • Lab or clinic appointments: appointments go out without moving patient or sample data into a third-party scheduler.
  • Reviews and approvals: handoffs and audit meetings are scheduled as part of the workflow that needs them.
  • Automated follow-ups: a contract approval or a finished milestone triggers the next meeting automatically.

Once basic invites work, the same pattern extends to updates (increase SEQUENCE), multiple attendees, cancellation notices, and logging every invite back to the record. If you want a history of who changed a meeting and when, the Audit Log & Version History add-on covers that side. For a closer look at the file-writing steps themselves, see exporting container data with the Data File script steps.

What this could look like in your solution

The useful version of this is not a button someone remembers to press. It is a meeting invite that goes out because a record reached a certain state: an inspection assigned, an order ready to ship, a review due. The calendar becomes an output of the system instead of a separate chore.

Kyo Logic builds custom Claris FileMaker and manufacturing software for businesses across New England and beyond. If you want help wiring invites into your own scheduling logic, handling time zones for a team spread across regions, or sending updates and cancellations cleanly, reach out.

Frequently asked questions

Can FileMaker send Outlook or Google Calendar invites?

Yes. FileMaker can create a standard iCalendar (.ics) file and email it as an attachment. Outlook, Apple Calendar, and Google Calendar recognize the file as a meeting invitation.

Do I need a plug-in or an outside API?

No. The add-on uses native FileMaker script steps. The Data File script steps that write the .ics file have been available since FileMaker Pro 18.

Why do invites show up at the wrong time?

Usually because of time zone handling. Writing start and end times in UTC with a trailing Z, and converting carefully from local time, avoids most of these problems.

Can I update or cancel an invite I already sent?

Yes. Send a new .ics file with the same UID and a higher SEQUENCE number to update an event. Cancellations follow the same pattern.

Quick takeaways

  • Use one UID per event and increase SEQUENCE on every change.
  • Write times in UTC and test with at least two calendar apps before rollout.
  • Fold any line longer than 75 octets, including long titles and descriptions.
  • Download the add-on and send a test invite to yourself before you connect it to real records.

Get the Calendar Invite Creator add-on

Tell us where to send it and we will email your download link right away.

Multi-File Uploader: drag and drop many files into a FileMaker record at once

Free FileMaker add-on

Multi-File Uploader: drag and drop many files into a FileMaker record at once

Attach photos, PDFs, spreadsheets, and drawings in one step, then preview, download, or delete them from a simple portal.

You can attach many files to a FileMaker record in one step. Out of the box, FileMaker inserts one file per action. Kyo Logic’s free Multi-File Uploader add-on adds a drag-and-drop window, so users can drop photos, PDFs, spreadsheets, and drawings onto a record together, then preview, download, or delete them from a portal.

Here is the moment it exists for. A field technician comes back from a site visit with 14 photos and a signed checklist. Attaching them one container at a time takes a dozen clicks per file, so the photos end up in an email thread instead of on the job record. Three months later, nobody can find the picture of the damaged panel.

What does the add-on do?

  • Upload many files at once to the record you are viewing: a customer, order, project, or ticket.
  • Preview, download, or delete uploaded files from a simple portal below the button.
  • Store files where you want. Files go into the included uploaderFiles table by default, or you can point storage at your own Documents or Files table.
  • Drop it onto any layout and link it to that layout’s primary key.

Day to day, it works like this:

A user clicks the Upload Files button on a record

↓

They drag and drop one or more files into the pop-up window

↓

They click Upload

↓

The files attach to the current record and appear in the portal below

Requirements and setup

The add-on needs FileMaker 19 or later, which is when Claris introduced add-ons. It works in hosted and local files. Setup takes about five minutes:

  1. Create the add-on. Open the downloaded file, click Create Add-on, and when the script finishes, close FileMaker.
  2. Install it. Reopen FileMaker and open the file you want to enhance. In Layout mode, open the Add-ons tab in the left pane, click the + button, and choose the uploader add-on. Drag its icon onto your layout.
  3. Tie uploads to your record. In the uploader_Upload File script, set the $id variable to the primary key of the layout’s base table, for example Customers::CustomerID or Jobs::JobID.
  4. Choose where files are stored. Keep the included uploaderFiles table, or update the storage steps in uploader_Upload File to target your own table and fields.

These steps are examples. Update layout names, table occurrences, field names, and privileges to match your solution, and test on a copy of your file before rolling it out.

How it fits real workflows

  • Field service and inspections: drop in the photos and checklist from a visit, no extra steps.
  • Sales and account records: keep proposals, statements of work, and change orders with the customer.
  • Operations and projects: store drawings, packaging specs, or vendor certifications on the job.
  • Quality checks: attach inspection photos and test reports to the lot or order they belong to.
  • Support tickets: attach screenshots and logs to speed up resolution.

Security, styling, and troubleshooting

Apply privilege sets so only the right roles can upload or delete files, and if you change the storage table, confirm accounts have the right record and field access. Restyle the button and portal to match your theme.

If something looks wrong, it is almost always one of four things:

  • Add-on not visible: confirm you ran Create Add-on and restarted FileMaker before installing.
  • Files linking to the wrong record: recheck the $id assignment in uploader_Upload File.
  • Files missing from your table: if you pointed storage at a custom table, recheck the storage steps and field mappings.
  • Portal looks empty: make sure the portal uses the correct related table occurrence and a relationship on your record’s primary key.

For power users: add a server-side cleanup routine for orphaned files when a record is deleted, add a counter to file names if you need versions, show a busy indicator for large uploads, or adapt the storage steps to write to S3 or Azure with signed download links. If you need to push files back out on a schedule, the Data File script steps handle that side, and the Rich Text Editor covers the notes that usually sit next to the attachments.

A thank-you

The Multi-File Uploader would not exist without Jason Wood’s work at Define Database. Jason originally built this tool for use with S3, and we adapted it for storage in FileMaker. Thank you, Jason.

What this could look like in your solution

The payoff is that documents stop living in inboxes. When attaching a file is as easy as dropping it on the record, people do it, and the record becomes the place to look. That matters most where proof is required later: inspections, deliveries, quality checks, and change orders.

Kyo Logic builds custom Claris FileMaker and manufacturing software for businesses across New England and beyond. If you want help dropping the add-on onto a layout, pointing it at your primary key, or moving storage into your existing documents table, a short working session is often enough. Reach out.

Frequently asked questions

Can FileMaker upload multiple files at once?

Not natively. FileMaker inserts one file per action. The free Multi-File Uploader add-on adds a drag-and-drop window so users can attach many files to a record in one step.

Which FileMaker version does the Multi-File Uploader need?

FileMaker 19 or later, since it is packaged as a FileMaker add-on. It works in hosted and local files.

Where are the uploaded files stored?

By default in the included uploaderFiles table. You can point storage at your own Documents or Files table by updating the storage steps in the uploader_Upload File script.

Why are my files attaching to the wrong record?

Check the $id variable in the uploader_Upload File script. It must use the primary key of the layout’s base table, such as Customers::CustomerID.

Quick takeaways

  • Pick the record type where people email files instead of attaching them, and start there.
  • Set $id to the primary key of the layout’s base table before anything else.
  • Decide whether files belong in the included table or your existing documents table.
  • Install on a copy of your file, test uploads and deletes with each privilege set, then roll out.

Get the Multi-File Uploader add-on

Tell us where to send it and we will email your download link right away.

Introducing the Communication Log (Free FileMaker Add-On)

Most teams track conversations in email threads, chat, and spreadsheets. When you need the full picture on a client, order, job, or ticket, context is scattered. A Communication Log centralizes those touchpoints right on the record, so anyone can see what was said, by whom, and when without leaving FileMaker.

You get: faster handoffs, fewer “did anyone call them?” moments, and an audit trail you can trust.

What you can do with it (examples)

  • Pin call notes, emails, and internal comments to any record
  • See a chronological timeline of interactions in one place
  • Load a log per customer, order, project, etc.

Requirements & compatibility

  • Works with modern FileMaker versions that support Add‑ons (FileMaker 19+).
  • Designed to drop onto any layout and point to your base table’s primary key
  • Ships with two helper scripts: dialog_Create Message and dialog_Load WebViewer

Quick start (5 minutes)

  1. Create the add‑on bundle
    • Download and open FileUploader-Addon.
    • Click Create Add‑on.
    • When the script finishes, close FileMaker.
  2. Install the add‑on into your app
    • Reopen FileMaker and open the target file.
    • In Layout mode, open the left pane → Add‑ons → Install Add‑on.
    • Select CommunicationLog and click Choose.
  1. Drop it into a layout
    • In the Add‑ons panel, drag the CommunicationLog onto the layout you want.
    • Restyle to match your theme (styles, fonts, colors).

 

  1. (Optional) Support multiple contexts
    • Open the script dialog_Create Message.
    • Replace the hard‑coded IDs on lines 10 and 20 with your layout’s primary key field (e.g., Customers::CustomerID).
    • This lets you reuse the add‑on on different layouts (Customers, Orders, Projects) and keep each log scoped correctly.
  2. Load behavior (recommended)
    • Trigger dialog_Load WebViewer on OnRecordLoad or OnLayoutEnter.
    • Pass the record’s primary key as a JSON parameter.
    • Use the example attached to the add‑on’s “Load Dialog” button as the source of truth for the correct JSON keys.
  3. Example (generic):
    // Script trigger parameter
    JSONSetElement ( “{}”
    ; [ “ID_LOG” ; YourTable::PrimaryKey ; 1]
    )

How it fits into real workflows

  • Sales/Account Management: Log calls and emails against a customer; see the full history before a renewal call.
  • Service/Support: Tie notes to a ticket; cut back on “who said what” confusion.
  • Operations/Projects: Keep vendor or internal coordination readable at a glance.

Styling tips

  • Create custom object styles for headings, timestamps, and message text to match your app.
  • Consider a light/dark background card for readability.
  • If the add‑on exposes buttons (add, filter, etc.), map them to your theme’s button style.

Security & deployment

  • Apply proper privilege sets so only the right users can add or edit messages.
  • Test on a copy of your file before deploying to users.

Troubleshooting

  • Add‑on doesn’t appear? Make sure you ran Create Add‑on and then restarted FileMaker before installing.
  • Web Viewer is blank? Confirm the dialog_Load WebViewer script is firing and that you’re passing the expected JSON key(s).
  • Messages not tied to the right record? Double‑check you replaced the hard‑coded IDs on lines 10 and 20 in dialog_Create Message with your primary key.

Download + next steps

Download the Communication Log (attached here)

Credentials for the demo: Admin / Admin (update before production).

Have 30 minutes? We’ll help you drop the add‑on into your file, point it at your primary key, and confirm the trigger/JSON parameter setup.

Appendix (for power users)

  • Consider calling the load script on both OnRecordLoad and OnLayoutEnter if you allow record switching and fast layout navigation.
  • If you need more than a single log per context (e.g., separate internal vs. external threads), duplicate the add‑on instance and drive each with a different context key.
  • Source control: version your add‑on bundle and keep a lightweight readme of local changes for your team.




Communication Log Add-on Download File

Please complete this form to download the FREE file.

This field is for validation purposes and should be left unchanged.
Name(Required)