An adaptive Dynamics 365 and Dataverse web resource that brings related operational context into the forms where work already happens.

The workflow before the build

A person working in a business record can have to open multiple forms or related lists to assemble the cases, orders, entitlements, contacts, and other context needed for the next action.

What the public project delivers

The public solution provides an adaptive JavaScript web resource for Dynamics 365 and Dataverse forms that retrieves and presents related entity context in one place.

  • Embeds a reusable web resource in Dynamics 365 or Dataverse model-driven forms.
  • Presents related entity information such as cases, orders, entitlements, and contacts.
  • Adapts the view to the current record and available related data.
  • Keeps the user in the host business application while they review context.

The value case, stated honestly

The design is intended to reduce context switching and make the surrounding record history easier to scan before a person chooses the next action.

Evidence label: Designed value: less navigation between related records and a more coherent operational view at the point of work.

Architecture in one view

A model-driven form passes record context to a web resource, which retrieves related Dataverse data for user review.

Customer 360 for Entities architecture A model-driven form passes record context to a web resource, which retrieves related Dataverse data for user review. 01 Current record 02 Web resource 03 Dataverse context 04 User action
01 / Current record

A model-driven form supplies the current entity and record context.

02 / Web resource

Client-side JavaScript initializes the adaptive experience.

03 / Dataverse

Approved queries retrieve related operational records.

04 / User action

The person reviews the unified context and remains responsible for the next action.

Human control and guardrails

  • The experience uses the host application's identity and Dataverse permissions rather than creating a separate authority boundary.
  • The component presents context; it does not replace the person's judgment or automatically commit consequential changes.
  • Deployers must limit queries and displayed fields to information users are already authorized to access.

Where the pattern stops

  • The solution requires configuration for each Dataverse schema, form, and relationship set.
  • Performance depends on query design, related-record volume, and the host environment.
  • The public repository is a community solution and not a Microsoft-supported product.

Explore the public proof