Enax - Developer Tools

Turn a specification into
D365 F&O metadata

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.

Up to 90%
Faster than manual development
Tables - Forms - Entities
Full AOT object generation
Encrypted
Specifications, end to end
What is DynaForge

Generate metadata from a specification

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.

How it works

Four steps, two tools

You design in the web builder; the Visual Studio extension does the building. The handoff between them is a single encrypted package.

1

Define

Describe tables, fields, indexes, relations, forms and data entities in the specification builder. Live validation catches mistakes as you type.

In the web app
2

Package or ticket

Export the specification as an encrypted .eax package, or attach it straight to an Azure DevOps work item for the developer.

In the web app
3

Generate

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 Studio
4

Review

The developer reviews the generated objects, adjusts business logic, and commits.

In Visual Studio
Capabilities

What DynaForge handles for you

Complete table modelling

Fields with EDTs, enums and primitives, string lengths, mandatory/visible flags, indexes (including unique) and table relations - all captured in one place.

Forms & data entities

Define form patterns with data sources and joins, and generate data entities with staging and keys for integration scenarios.

Encrypted handoff

Export specifications as encrypted .eax packages for handoff.

Built-in validation

The builder flags incomplete or conflicting definitions before you import the specification into Visual Studio.

Azure DevOps integration

Create a work item with a professional implementation-plan description and the encrypted specification attached - straight from the builder.

Effort estimation

See a realistic manual-development estimate versus the DynaForge time before you commit, based on the actual artifacts in your project.

Estimate the work before development

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.

Manual development 14 - 23 hours
With DynaForge ~2 hours
Time saved Up to 90%
User manual

Using DynaForge, step by step

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.

1

Open the builder

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.

2

Describe your objects

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.

3

Validate

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.

4

Export data or create a ticket

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.

5

Resume later if needed

Coming back to an existing package? Use Import Existing Data to load a previously exported .eax and continue where you left off.

6

Import in Visual Studio

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.

7

Generate & review

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.

Good to know

Common questions

Do I need the Visual Studio extension?

The web builder is free to design and export specifications. Generating the actual AOT objects in Visual Studio requires the licensed DynaForge extension.

Is my specification secure?

Yes. Packages are encrypted and are never stored or transmitted in plain text between the web app and the extension.

Which objects are supported?

Tables (with fields, EDTs, enums, indexes, relations), forms with data sources, and data entities. The set grows with each release.

Do I have to use Azure DevOps?

No. Azure DevOps integration is optional. You can simply export the encrypted package and hand it to a developer directly.

Design once. Generate the rest.

Start describing your D365 F&O objects and let DynaForge handle the build.

Create your free account