soneta-business-xml

Generate XSD-compliant Soneta business.xml definitions for modules, tables, and relations.

9|6|Updated Dec 26, 2025

Search Tags:#code-generation #module-definition #soneta #enova365 #business-xml #xml-schema

Ready to run

npx skills add https://github.com/soneta/soneta-erp-skills --skill soneta-business-xml

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: soneta-business-xml
Source: https://github.com/soneta/soneta-erp-skills/tree/main/soneta-business-xml
Command: npx skills add https://github.com/soneta/soneta-erp-skills --skill soneta-business-xml

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill generates standardized Soneta business.xml definitions (modules, tables, columns, and relations) that conform to the XSD schema, reducing manual XML drafting and ensuring consistency across modules.

Core Features & Use Cases

XML generation for business.xml from module-level specifications (name, namespace) and object definitions.
Schema compliance with enova365/Soneta's business_struct.xsd and cross-module references.
Use Case: When designing a new business module, provide the module name, namespace, and core tables to automatically produce a ready-to-use business.xml.

Quick Start

Utwórz moduł o nazwie "Zasoby" i wygeneruj szkielet pliku business.xml.

Frequently Asked Questions about soneta-business-xml

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a business.xml file for a new enova365 module?▼

To generate a business.xml file for a new enova365 module, provide the module name, namespace, and core table definitions. The Skill outputs an XSD-compliant XML skeleton with correct entities and relationships.

What is the correct way to define tables and relations in Soneta business.xml?▼

Defining tables and relations in Soneta business.xml requires structuring object definitions according to the enova365 business_struct.xsd schema. This ensures correct namespace naming and valid cross-module references.

Does the Soneta business.xml generator enforce XSD schema compliance?▼

Yes, schema compliance is enforced during business.xml generation. The Skill validates module definitions, tables, columns, and relations against the enova365/Soneta business_struct.xsd to prevent invalid XML files.

Can I use this to refine existing object definitions in a business.xml file?▼

Yes, you can refine existing object definitions by specifying the updated entities, relationships, and schemas. The Skill regenerates the business.xml definitions while maintaining strict adherence to the Soneta XSD schema.

Why does my manually drafted Soneta business.xml fail XSD validation?▼

Manually drafted business.xml files often fail XSD validation due to incorrect namespace naming or malformed cross-module references. Automating definition generation ensures structural adherence to the enova365 schema requirements.

Do I need to specify the namespace when creating a business.xml module definition?▼

Yes, specifying the namespace is required when creating a business.xml module definition. The Skill uses the module name and namespace to automatically produce correctly named and XSD-compliant XML elements.