FileMaker OttoFMS icon

FileMaker OttoFMS

Execute FileMaker scripts, request data, and manage data via OttoFMS DataAPI Proxy
Join our community

Actions7

Overview

This node enables interaction with FileMaker databases via the OttoFMS DataAPI Proxy. Specifically, the "Record" resource with the "Delete" operation allows users to delete a record from a specified FileMaker table by providing the primary key of that record. This is useful in scenarios where you need to programmatically remove outdated or incorrect data entries from your FileMaker database.

Practical examples include:

  • Automatically deleting customer records that have unsubscribed.
  • Removing test or temporary data after processing.
  • Cleaning up records based on external triggers or workflows.

Properties

Name Meaning
Table Name The name of the FileMaker table (Table Occurrence) from which the record will be deleted.
Primary Key The primary key value identifying the specific record to delete (e.g., "123" or "ABC-456").

Output

The node outputs JSON data representing the result of the delete operation. Typically, this includes confirmation of deletion or any error messages returned by the FileMaker API proxy. The output does not include binary data.

Example structure might look like:

{
  "success": true,
  "deletedRecordId": "123",
  "message": "Record deleted successfully."
}

If the deletion fails, the output will contain error details explaining the failure.

Dependencies

  • Requires an API key credential for authenticating with the OttoFMS DataAPI Proxy.
  • The node expects the FileMaker server to be accessible through the configured proxy endpoint.
  • Proper permissions on the FileMaker side to delete records in the specified table.

Troubleshooting

  • Common issues:

    • Incorrect table name or primary key value leading to "record not found" errors.
    • Insufficient permissions to delete records in the target FileMaker table.
    • Network or authentication failures connecting to the OttoFMS DataAPI Proxy.

  • Error messages and resolutions:

    • "Record not found": Verify the table name and primary key are correct and exist in the database.
    • "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has necessary access rights.
    • "Network error" or "Timeout": Ensure the proxy endpoint is reachable and there are no firewall restrictions.

Links and References

Discussion