frappe-syntax-serverscripts

To write Frappe Server Scripts safely without import blocking errors, you must use the pre-loaded frappe namespace and avoid all import statements. The sandboxed environment blocks imports to ensure secure execution across Document Events and API endpoints.

Frappe Server Scripts require correct event name mappings for Document Events, Scheduler Events, and Permission Queries. Using the proper event mappings ensures your script triggers execute correctly and maintains syntax compatibility across Frappe v14 through v16.

No, you cannot use Python imports in ERPNext Server Scripts because the sandbox environment strictly blocks import statements. You must rely entirely on the pre-loaded frappe namespace and its sandbox-safe utilities to execute business logic.

Sandboxed Server Scripts are supported across Frappe versions 14, 15, and 16. This compatibility ensures that your event mappings, API endpoints, and permission queries maintain consistent syntax and behavior throughout the Frappe v14–v16 lifecycle.

The Frappe Server Script sandbox prohibits import statements and restricts execution to the pre-loaded frappe namespace. This limitation prevents unauthorized access and ensures scripts only use sandbox-safe utilities for Document Events and Scheduler Events.

To call Frappe API endpoints safely from a Server Script, reference the pre-loaded frappe namespace directly without importing external modules. This approach adheres to sandbox rules and ensures secure, compliant API endpoint execution.