frappe-syntax-serverscripts

To write a Frappe Server Script without imports, rely entirely on the pre-loaded `frappe` namespace and whitelisted utilities. Avoiding imports is required because the RestrictedPython sandbox blocks them to prevent unsafe operations.

Calling `doc.save()` inside a 'Before Save' event causes a recursive loop and production failure. 'Before Save' maps to the internal `validate` hook, so you must modify properties directly without triggering another save action.

To map Frappe Server Script UI event labels to internal lifecycle hooks, match the UI selection to the underlying docstate action, such as mapping 'Before Save' to the `validate` hook or 'After Insert' to `on_update`.

You cannot use `frappe.db.commit()` in ERPNext Document Event Server Scripts. Manual commits are restricted, but Scheduler event scripts require applying specific commit rules to ensure database transactions are finalized safely.

The correct way to run parameterized SQL in Frappe Server Scripts is to use the pre-loaded `frappe.db.sql` method with standard parameter binding. This ensures SQL safety by preventing injection within the RestrictedPython sandbox.

RestrictedPython sandbox rules block standard libraries in Frappe Server Scripts by restricting all import statements. Developers must use only the pre-loaded `frappe` namespace and approved whitelisted utilities to execute logic safely.