DynaForge lets D365 Finance & Operations consultants describe tables, forms and data entities in a simple editor, then generates the matching AOT objects inside Visual Studio — no hand-coding, no copy-paste, no missed properties.
On a D365 F&O project, a consultant designs the data model and a developer builds it by hand in Visual Studio — slow, repetitive, and easy to get wrong. DynaForge captures the design once, as a structured specification, and the Visual Studio extension turns that specification into the real AOT objects. The consultant stays in charge of the design; the mechanical work is automated.
You design in the web builder; the Visual Studio extension does the building. The handoff between them is a single encrypted package.
Describe tables, fields, indexes, relations, forms and data entities in the specification builder. Live validation catches mistakes as you type.
In the web appExport the specification as an encrypted .eax package, or attach it straight to an Azure DevOps work item for the developer.
The Visual Studio extension imports the package and generates the matching D365 F&O AOT objects — tables, EDTs, enums, indexes, relations, forms and entities.
In Visual StudioThe developer reviews the generated objects, adjusts business logic, and commits. Hours of boilerplate become minutes of review.
In Visual StudioFields with EDTs, enums and primitives, string lengths, mandatory/visible flags, indexes (including unique) and table relations — all captured in one place.
Define form patterns with data sources and joins, and generate data entities with staging and keys for integration scenarios.
Specifications travel as encrypted packages. .eax packages. The design never leaves your control in plain text.
Contradictory or incomplete definitions are flagged before you ever reach Visual Studio, so generation runs clean the first time.
Create a work item with a professional implementation-plan description and the encrypted specification attached — straight from the builder.
See a realistic manual-development estimate versus the DynaForge time before you commit, based on the actual artifacts in your project.
Every specification comes with an effort estimation: how long the same objects would take to build by hand versus with DynaForge. It weighs the number and complexity of your artifacts — fields, EDTs, enums, indexes, relations — not just raw counts. Deterministic, consistent, and honest.
From a blank editor to generated objects. Steps 1–5 happen here on the web; steps 6–7 happen in Visual Studio with the licensed extension.
Sign in and choose Create Technical Document (D365 FO + DevOps). Click Sample any time to load a worked example, or Create Object to start from scratch.
Add tables and their fields, indexes and relations; add forms with data sources; add data entities. Use Edit Object to change anything — updates rewrite the definition cleanly without duplicating it.
Watch the Validation panel. It flags issues such as a missing string length or a contradictory index before you export. Fix them until it reads clean.
Use Export Data to download the encrypted .eax package, or Create DevOps Ticket to open an Azure DevOps work item with the package attached and an auto-generated implementation plan. Toggle Show in the ticket to include the effort estimation in the description.
Coming back to an existing package? Use Import Existing Data to load a previously exported .eax and continue where you left off.
Open the DynaForge extension in Visual Studio, click Import Package, and select the .eax file (or the attachment from the DevOps ticket). The extension decrypts and previews every artifact.
Run generation to create the AOT objects in your model, then review and add business logic. What used to be hours of boilerplate is now a short review.
The web builder is free to design and export specifications. Generating the actual AOT objects in Visual Studio requires the licensed DynaForge extension.
Yes. Packages are encrypted and are never stored or transmitted in plain text between the web app and the extension.
Tables (with fields, EDTs, enums, indexes, relations), forms with data sources, and data entities. The set grows with each release.
No. Azure DevOps integration is optional. You can simply export the encrypted package and hand it to a developer directly.
Start describing your D365 F&O objects and let DynaForge handle the build.
Create your free account