Manage DAT Package — Lifecycle .dat пакета

What problem does it solve?

Directum RX .dat packages often fail import or behave inconsistently because of metadata inconsistencies (GUIDs, resx keys, navigation references, enum values, attachment constraints) and packaging mistakes; this Skill provides a repeatable lifecycle to validate, auto-fix, build, and deploy the package to a Directum RX stand.

Core Features & Use Cases

• End-to-end .dat lifecycle: runs validate → fix → build → deploy_to_stand to produce and publish a correct DirRX.Solution.dat artifact.
• Guardrailed validation: performs 14 automated checks for common DDS import failure causes (e.g., CollectionPropertyMetadata, NavigationProperty consistency, reserved enum values, System.resx key alignment).
• Deterministic auto-fixes: applies safe corrections such as System.resx key renaming (Resource_<GUID> → Property_<Name>), deduplicating DB column Code, and synchronizing AttachmentGroup constraints, typically using dry-run first.
• Build and packaging: builds the output .dat from PackageInfo.xml and the expected source/settings structure, with a zip-based fallback description.
• Deploy with modes: deploys to the stand with dry-run and apply/confirm flow, supporting dev/full/init/settings modes depending on what you changed.

Quick Start

Ask the AI to validate, auto-fix, build, and deploy your Directum RX CRM .dat package by running the check_package, fix_package (dryRun then apply), build_dat, and deploy_to_stand steps for PackageInfo.xml located in your CRM package directory.