1. What you can do with the ACF plugin without ACF programming

Many FileMaker developers first meet the ACF plugin as a way to write compiled ACF packages. That is the larger story, but it is not the only story.

After the plugin is installed, FileMaker also gets a useful set of calculation functions that can be used directly in fields, scripts, button actions, conditional hiding, portal sorting, data import/export, translation workflows, dialogs, progress windows, and document handling. You can use these features without writing a single ACF function yourself.

The practical idea for this video is simple: open FileMaker's calculation dialog, type part of an ACF function name, and use the plugin as a toolbox.

1. What you can do with the ACF plugin without ACF programming
   1. The two built-in toolboxes
   2. Get the complete list from your own plugin
   3. Read and write files
   4. Build text exports line by line
   5. Work with paths
   6. Format numbers and control digits
   7. Save logs from scripts
   8. Copy documents from a document store
   9. Use the plugin's built-in FileMaker functions
   10. Queue messages with AMQP and RabbitMQ
       1. ACF_AMQP_Initialize
       2. ACF_AMQP_Send
       3. ACF_AMQP_Listen
       4. ACF_AMQP_Close
   11. Portal sorting without ACF programming
   12. Translation workflows
   13. Progress windows and dialogs
   14. Drag and drop zones
   15. Video outline
   16. Summary

1.1. The two built-in toolboxes ↑

There are two groups of functions worth knowing about:

• The plugin's built-in functions, such as dsPD_Version, ACF_GetAllPrototypes, ACF_OpenDialog, ACF_ProgressOpen, _, and _n.
• The preloaded Bootstrap package, exposed in FileMaker with the ACFU_ prefix, such as ACFU_LoadFile, ACFU_SaveFile, ACFU_SelectFolder, and ACFU_NumFormat.

The Bootstrap package is always present in current plugin versions. Its source is available online on this site and in the ACF library, but you normally do not need to open or modify that file. The assigned FunctionID values make most Bootstrap functions available directly from FileMaker calculations by adding the ACFU_ prefix.

Example:

Set Variable [ $text ; ACFU_LoadFile ( $path ) ]

That calls the Bootstrap LoadFile function. No ACF source code, compile step, or package loading is needed.

1.2. Get the complete list from your own plugin ↑

The fastest way to see what is installed in your current environment is:

Set Field [ Preferences::Prototypes ; ACF_GetAllPrototypes ]

This returns the prototypes for installed packages and functions. It is also a good cut-and-paste source when writing FileMaker calculations.

For the Bootstrap package, the output uses names like:

ACFU_LoadFile ( text_filename )
ACFU_SaveFile ( text_filename ; text_content )
ACFU_SelectFolder ( text_prompt )

All loaded ACF functions can also be called with ACF_run, for example:

ACF_run ( "bootstrap_AreWeLoaded" )

For everyday FileMaker script work, the direct ACFU_ form is usually easier to read, and it also offers autocomplete in the workspace.

1.3. Read and write files ↑

The Bootstrap functions give FileMaker scripts direct access to common file operations:

This is useful for import/export features, developer tools, preference setup, template handling, and support scripts where users need to choose source or destination files.

1.4. Build text exports line by line ↑

For larger exports, it is often better to open a file once, write many lines, then close it.

Set Variable [ $file ; ACFU_SaveFileDialogue ( "Save export" ; "" ; "export.txt" ) ]
If [ $file <> "" ]
    Set Variable [ $fileNo ; ACFU_OpenOutputFile ( $file ) ]
    Set Variable [ $res ; ACFU_WriteOutputWinFileUTF8 ( $fileNo ; "Header" & Char ( 13 ) ) ]
    # Loop records here and write one line per record.
    Set Variable [ $res ; ACFU_CloseFile ( $fileNo ) ]
End If

The Bootstrap package includes write helpers for Mac UTF-8, Windows UTF-8, and Windows ISO-8859-1 text output:

1.5. Work with paths ↑

Path handling is a common source of small FileMaker script errors, especially in mixed Mac and Windows environments. These helpers make it easier:

Example:

ACFU_GetPlatformString (
    "ArchiveDisk:Documents";
    "\\server\ArchiveDisk\Documents"
)

1.6. Format numbers and control digits ↑

Some functions are immediately useful in ordinary FileMaker calculations:

Example:

"NOK " & ACFU_NumFormat ( Invoice::Total ; "," )

1.7. Save logs from scripts ↑

When troubleshooting a customer solution, it is helpful to write log text to a known location:

This lets a FileMaker script build a support log without requiring a custom export routine for every case.

1.8. Copy documents from a document store ↑

ACFU_BSBO_SaveDocumentDesktop ( docStore ; archiveSubPath ; title ) is designed for document archive solutions.

A typical portal row can have a button called "Copy to desktop". The function combines a configured document store path with a relative archive path, then copies the selected file to the user's desktop. If the user holds the Alt key, the function opens a Save dialog so the user can choose another destination.

This is especially useful in mixed Mac and Windows installations when combined with ACFU_GetPlatformString.

1.9. Use the plugin's built-in FileMaker functions ↑

These are the built-in plugin external functions available from calculations. Several of them are useful even when you are not writing ACF code.

The ACF package management functions are included here because you can use existing packages without authoring them. For example, a developer may provide a compiled package, and the FileMaker solution can install and run it.

Use ACF_GetAllPrototypes in the installed plugin as the final truth for what your FileMaker solution can call.

1.10. Queue messages with AMQP and RabbitMQ ↑

AMQP, Advanced Message Queuing Protocol, is a standard protocol for sending messages through a message broker. RabbitMQ is a popular open-source AMQP broker. The broker sits between the sender and the receiver: FileMaker, a web shop, PHP, Python, or another system can send a small message to RabbitMQ, and another process can consume the message when it is ready.

This is useful when you do not want every event to trigger immediate heavy work. Instead of a FileMaker script calling a web API 100 times in a burst, the script can send 100 small messages quickly. RabbitMQ keeps the queue, and the worker side processes one or a few messages at a time. This makes the user interface feel faster and protects FileMaker Server, web servers, and external APIs from sudden load spikes.

AMQP support was available in the old 1.6.x plugin under the dormant dsPD_AMQP_* names. It has now been reintroduced in plugin version 1.8.0.2 with the current ACF_AMQP_* names.

Typical use cases:

• Notify a web solution that a FileMaker record has changed, then let the web worker pull the updated data.
• Let a web shop send a message when a new order arrives, so a FileMaker client or server-side process can handle the order.
• Queue many browser/UI events, such as moving blocks in a web interface, and let FileMaker process them later when idle.
• Send print jobs to a FileMaker client connected to a USB label printer at a packing line.
• Decouple slow integrations from user-facing scripts, so the user does not wait for each external call.

The AMQP functions can be used directly from FileMaker calculations and scripts:

1.10.1. ACF_AMQP_Initialize ↑

ACF_AMQP_Initialize ( broker ; user ; password ; port )

Parameters:

The function stores the connection settings and returns a short broker description, for example:

Broker: amqp://acf:**@127.0.0.1:5672//

Example:

Set Variable [ $$AMQP ; ACF_AMQP_Initialize ( "127.0.0.1" ; "acf" ; "acf_dev_password" ; "5672" ) ]

1.10.2. ACF_AMQP_Send ↑

ACF_AMQP_Send ( functionName ; parameterList ; Queue ; routingKey ; QueueType ; recipientType )

Parameters:

Return value:

• OK when the message was published.
• A plugin error result if the broker cannot be reached or the message cannot be sent.

Example:

Set Variable [ $payload ; "client1¶Order¶12345¶manual test" ]
Set Variable [ $res ; ACF_AMQP_Send ( "acf.test.echo" ; $payload ; "celery" ; "celery" ; 1 ; 1 ) ]

In a web-shop integration, the payload could contain the shop name, order id, and action. A FileMaker listener can then pick up the message and run the order-processing script.

1.10.3. ACF_AMQP_Listen ↑

ACF_AMQP_Listen ( Queue ; QueueType ; fmScript ; timeout )

Parameters:

Return value when no script is supplied:

task
message-id
arg1
arg2
...

Example, wait up to five seconds and return one message:

Set Variable [ $message ; ACF_AMQP_Listen ( "celery" ; 1 ; "" ; 5 ) ]

Example, start a persistent listener:

Set Variable [ $$AMQP_Listen ; ACF_AMQP_Listen ( "labelPrint" ; 1 ; "Handle label print message" ; 0 ) ]

The persistent listener records which FileMaker file started it. If several files are open in the same FileMaker client, this prevents the listener from accidentally calling a script in the wrong file. Only the owning file should close the listener.

1.10.4. ACF_AMQP_Close ↑

ACF_AMQP_Close()

Stops the persistent AMQP listener for the current FileMaker file and releases the listening channel.

Example:

Set Variable [ $res ; ACF_AMQP_Close() ]

Use this in shutdown scripts, when changing queue configuration, or before starting a different listener in the same FileMaker client.

1.11. Portal sorting without ACF programming ↑

Two small functions are useful for dynamic portal sorting:

dsPD_Text2Hex ( text )
dsPD_Text2HexInv ( text )

dsPD_Text2Hex converts text into a hexadecimal representation. dsPD_Text2HexInv produces an inverted value. This means one calculation field can support ascending and descending portal sort order while the FileMaker portal itself remains sorted ascending.

Example idea:

Let ( [
    v = Customer::Name
] ;
    If ( Customer::SortDirection = 1 ;
        dsPD_Text2Hex ( v ) ;
        dsPD_Text2HexInv ( v )
    )
)

That is a practical plugin feature before you start writing custom ACF functions.

1.12. Translation workflows ↑

The plugin also exposes gettext-style translation functions:

_ ( "Invoice" )
_n ( "1 file" ; "%1 files" ; $count ; $count )
ACF_Load_TranslationPO ( $poFileOrContainer )
ACF_Clear_Translation
ACF_UpdatePOT ( $sourcePOT )

This gives FileMaker calculations a compact way to translate labels and messages. Plural handling is built in with _n.

1.13. Progress windows and dialogs ↑

For long-running FileMaker scripts, the progress functions can show status:

Set Variable [ $h ; ACF_ProgressOpen ( "Export" ; "Preparing..." ; 100 ) ]
Set Variable [ $res ; ACF_ProgressUpdate ( $h ; 50 ; "Half way" ) ]
Set Variable [ $res ; ACF_ProgressClose ( $h ) ]

For structured user input, the dialog functions use JSON:

ACF_OpenDialog ( $dialogJSON )
ACF_DialogApplyValues ( $dialogJSON ; $valuesJSON )

These are plugin features that can be used from FileMaker scripts and calculations. The JSON can be stored in fields, variables, or generated by script.

1.14. Drag and drop zones ↑

The drag-and-drop functions let a FileMaker layout define drop zones and callbacks:

ACF_DefineDragAndDrop ( $coords ; $callback ; $optionsJSON )
ACF_UpdateDragAndDrop ( $handle ; $coords )
ACF_RemoveDragAndDrop ( $handle )

These are client-side interface helpers, so they are intended for FileMaker Pro user sessions rather than server-side script execution.

1.15. Video outline ↑

Here is a simple flow for the video:

1. Open with the message: "You can benefit from the ACF plugin before writing ACF code."
2. Show ACF_GetAllPrototypes and explain that it is the live function list from the installed plugin.
3. Demonstrate ACFU_SelectAndGetFile, showing both the returned file content and $$FileName.
4. Demonstrate ACFU_SaveFileDialogue, ACFU_OpenOutputFile, one write call, and ACFU_CloseFile.
5. Show path helpers: filename, directory, and extension from the same selected path.
6. Show ACFU_NumFormat and one control digit function in the Data Viewer.
7. Show dsPD_Text2Hex and dsPD_Text2HexInv as the basis for portal sorting.
8. Show the progress window functions in a short loop.
9. Close by saying that ACF programming is the next level, but the plugin already adds a practical FileMaker toolbox on day one.

1.16. Summary ↑

Without writing ACF source code, the plugin can already help with:

• File selection and file content import.
• Text export and platform-specific line endings.
• Path parsing and cross-platform path configuration.
• Number formatting and control digits.
• Script logging.
• Document store copy-to-desktop workflows.
• Portal sorting helpers.
• Translation functions.
• Progress windows, dialogs, and drag-and-drop interaction.
• Installing and running prebuilt ACF packages.

That makes the ACF plugin useful both as a developer tool and as a runtime toolbox for ordinary FileMaker solutions.