Wizard: EDT
Wizard walkthrough · Core Studio 3.0 · Verified 2026-09-01
When to use it: you need a new extended data type — standalone, or extending a Microsoft base EDT to inherit its behavior.
Size: S · Automatable: fully.
Prerequisites
None beyond a custom model. If you’re extending, the index should be at tier ≥3 so the extends-picker lists Microsoft base EDTs.
Steps
- Basics — name (validated, collision-checked), model/module.
- Type family — String / Int / Int64 / Real / Date / UtcDateTime / Guid / Container…
- Family-specific properties — stringSize (default 10 for String), decimals, extends-picker from the index.
- Label / help / configuration key.
- Summary — preview, commit.
Output anatomy
AxEdt/<YourEdt>.xmlunder<root>/<Model>/<Module>/AxEdt/— re-indexed and immediately usable as a Table wizard field type or in code.
Verify it worked
- The EDT round-trips losslessly (including
ExtendsandLabel). - On-VM compile 0/0; pick it as a field type in the Table wizard on the next pass and it appears in the picker.
If it goes wrong
- Extends-picker is empty or degraded — the index hasn’t parsed Microsoft models yet (tier <3); wait for convergence or type the base EDT name and let the build verify it exists.
Next: Table wizard (its field step can co-generate EDTs through this same builder).