Accelerator catalogueHow we buildProduct storiesAbout SparrofoxDiscuss a process

For Dataverse and Dynamics 365 delivery teams

Develop and support Dynamics 365 through your AI assistant.

Flownominal brings Dataverse context and practical development tools into your compatible AI chat. Inspect the existing setup, work through a reviewable plan, apply supported changes within the agreed access, and keep the evidence for handover.

For developers, technical consultants and advanced makers working with Dataverse and the Dynamics 365 apps built on it.

Actual Flownominal ERD Studio showing a fictional Dataverse model with grouped relationships and clickable counts.
One view of the work: tables and relationships in a fictional Dataverse example.

Actual product screens · fictional metadata

Look inside the ERD Studio.

Explore a fictional model connecting accounts, contacts, projects and teams. Add or remove an entity, open a relationship count, then try the filters.

Each screenshot shows a fictional selection. The screens use different selections and counts; they are not a controlled comparison.

Actual Flownominal ERD Studio with fictional metadata. Choose entities and see grouped relationships.
Choose entities and see grouped relationships.
View the full screenshot

Start with the entities that matter

Choose the entities to include. Their relationships appear together in the diagram.

Open the relationship details

Relationships are grouped between entity pairs. Open a 1:N, N:1 or N:N count to inspect the definitions.

Filter the detail

Show the fields that matter, including lookups and fields used on forms. Custom and required-column filters are available too.

Take the diagram with you

Export a PDF with your chosen diagram and columns, plus an optional relationship appendix.

Try the ERD demo

Compatible AI connections · supported actions

Give your AI the context to do useful work.

Inspect tables, columns, relationships, forms, JavaScript and related solution context before deciding what needs to change. Explore the same work in the visual workspace and your compatible AI conversation.

Turn a request into a reviewable plan.

Capture the problem, proposed fix, supported steps and acceptance checks. Review the plan for the chosen environment, then apply the authorised scope through the supported tools.

Keep the change and its handover together.

Retain operation receipts, read-back observations and reported test evidence as separate records. Export a useful handover for the next developer, support person or reviewer.

A workspace for projects and everyday support.

Illustrative workflows, not customer case studies

Connect the right environment. Agree the right access.

MCP permissions are scoped to the selected connection and do not elevate the signed-in account’s Dataverse privileges. Confirm the compatible client, environment, permitted actions and result checks before use.

Using a connected workspace

Flownominal brings compatible AI chat and a development workspace together to explore existing Dataverse components, review supported change proposals and retain progress and handover evidence. Start with one task in an existing or independently selected Dataverse development environment. Agree the operator, environment, access, compatible client and supported operation before an evaluation. Saved connections and saved workspace artifacts, including snapshots and audit records, are shared within the operator workspace; customer access and hosting arrangements need separate agreement and checks.

Saved workspace artifacts do not mean customer business records are stored here. Exact access, operations and customer fit need confirmation.

Discuss an integration taskBrowse the catalogue
Entity canvas · fictional metadata
Actual Flownominal ERD Studio with fictional metadata. Choose entities and see grouped relationships.

Choose entities and see grouped relationships.

Agree the next scoped step

Discovery, implementation, licences, usage and optional support are agreed separately.

1. Explore and discuss

Find a relevant foundation and one process. Explore what it covers and its readiness, then check the fit against your current tools.

2. Agree discovery

Agree a paid discovery to examine one process, compare your current approach and define the deliverable, fit and acceptance criteria.

3. Approve implementation

Approve a separate implementation scope and price before configuration or adaptation begins. Your team reviews the agreed output before handover.

4. Handover and optional support

Your team reviews the agreed output and receives the agreed training and operating guidance. Ongoing support is optional and separately agreed. Product licences, third-party licences and usage costs are listed separately.

Explore the development workspace

Agree a compatible client, operator, development environment and supported task before evaluation. The existing app destination is preserved; this page does not establish current runtime parity.

Open Flownominal

Saved workspace artifacts do not mean customer business records are stored here. Exact access, operations and customer fit need confirmation.