Erpnext Impl Serverscripts

What it does

This skill enables an AI agent to assist in determining how to implement server-side features within ERPNext. It helps users decide between using a Server Script or a Controller for their desired functionality, guiding them based on factors like the need for external libraries or complex transactions. This skill is compatible with ERPNext versions 14, 15 and 16. Crucially, it highlights limitations regarding imports within server scripts.

When to use it

• When you're unsure whether to implement a feature using an ERPNext Server Script or a Controller.
• For quick prototyping of features directly within your ERPNext system without creating a custom app.
• If you need guidance on how to access pre-loaded namespaces instead of importing modules in server scripts.

Key capabilities

• Provides decision support for choosing between Server Scripts and Controllers in ERPNext.
• Identifies scenarios where a Controller (within a custom app) is more appropriate than a Server Script.
• Offers guidance on working within the limitations of server script imports, emphasizing the use of pre-loaded namespaces.
• Compatible with ERPNext versions v14, v15 and v16

Example prompts

• "Should I use a Server Script or Controller to [briefly describe desired functionality]?"
• "I need to access frappe.utils.nowdate() in an ERPNext server script. How do I do that?"
• “What are the limitations of using server scripts for implementing features?”

Tips & gotchas

• Import Restrictions: Be aware that Server Scripts have strict limitations on imports (e.g., import json, from frappe.utils import). Use pre-loaded namespaces directly instead.
• Controller Recommendation: For complex tasks requiring external libraries or robust error handling, a Controller within a custom app is recommended.
• Syntax Reference: Refer to the erpnext-syntax-serverscripts skill for detailed syntax information related to ERPNext server scripts.