Skip to content

Get better script results

Name the script and say whether you want an explanation, an edit, or a new script. Describe the expected behavior and what must stay unchanged.

In Export Orders, stop if the export fails and show the FileMaker error. Keep the existing file path and field order. Prepare the change for review.

For a new script based on an existing one, name the source and the new script separately.

  • Choose the model and reasoning effort in Settings. Reasoning guide.
  • Use exact script, table, and field names. Genie reads relevant context as needed.
  • Remove unrelated attachments. If Privacy is on, select the metadata Genie needs in Metadata Explorer.
  • Answer clarification questions with the missing detail.

Check the target and the complete proposed script before you use it. On a paid plan, use Preview. Create or apply only the change you intend, then test a normal case and a failure case in FileMaker. For several independent changes, review each result separately.

If the answer is incomplete, identify what is missing and continue the conversation. Adding more unrelated context usually makes the task harder to follow.

Genie checks each proposed script before it offers Create or Apply. While it prepares the result, it can fix some structural problems on its own. It stays within what you asked for: it does not add other scripts or broader changes to fix a problem.

If Genie cannot safely write the change in FileMaker, Apply is not offered, even when the script is shown. Use Preview and Copy to read the script and paste it yourself, or make the request more specific and send it again.

A warning means the result can be reviewed but has a limitation or a possible problem. Read it before you use the result. Some warnings include an error code. Use Error codes and recovery to find likely causes and next steps.

If the result leaves out part of what you asked for, Genie probably did not have enough detail. Name the exact script, tables and fields, answer Genie’s questions, and send the request again.

  • Be specific: name the target script and describe the expected behavior.
  • Read warnings and assumptions before you create or apply.
  • Compare the result to your intent in Preview, especially after a warning.
  • Use Refresh Selection when your request depends on the lines selected in Script Workspace.
  • Decide unclear business rules yourself. Genie should not guess them.
  • After you create or apply, check the script in FileMaker and test it.

Create and edit scripts · FileMaker context · Local MCP.