Solution entry · Business applications
Customer 360 for Entities
An adaptive Dynamics 365 and Dataverse web resource that brings related operational context into the forms where work already happens.
What changed in the design.
Customer-neutral framing keeps the pattern reusable without claiming private results.
Before the solution
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 was built
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.
Value enabled
The design is intended to reduce context switching and make the surrounding record history easier to scan before a person chooses the next action.
How the public pattern fits together.
A model-driven form passes record context to a web resource, which retrieves related Dataverse data for user review.
A model-driven form supplies the current entity and record context.
Client-side JavaScript initializes the adaptive experience.
Approved queries retrieve related operational records.
The person reviews the unified context and remains responsible for the next action.
What the project demonstrates.
- 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 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.
- 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.
Follow the evidence.
These public sources support the entry. No private customer material or internal evidence was used.
- Customer 360 for Entities public repository Public README, deployment guidance, web-resource source, and solution files are the evidence base for this entry.
- GitHub public repository metadata Repository created 2026-04-30; last public push 2026-08-26. These are repository facts, not adoption evidence.