This series builds a practical customer service workspace in a canvas app connected to Dynamics 365 Customer Service through Dataverse. The goal is not to replace the full Customer Service application. It is to provide a focused experience for agents, supervisors, or field teams who need to review and update cases quickly.
1. Define the user journeys
- Agents view cases assigned to them or their team.
- Agents open a case, review the customer and timeline context, and update status, priority, and resolution notes.
- Supervisors monitor unassigned, high-priority, and aging cases.
- Users create follow-up activities and record customer interactions.
2. Dataverse tables
Use the standard Case table (logical name incident) and related Account (account), Contact (contact), Queue (queue), and Activity tables. Add a custom table only when the requirement is not already represented by a standard column or relationship—for example, a structured site-visit assessment.
3. Suggested app structure
- My Cases: assigned active cases.
- Team Queue: cases requiring triage, subject to the user’s Dataverse privileges.
- Case Details: customer, subject, description, priority, status, owner, and activities.
- Supervisor Dashboard: counts by priority, status, and age.
4. Security and ownership
Canvas app visibility is not a security boundary. Configure Dataverse security roles, business-unit scope, team membership, and record ownership so users can access only the records they are authorized to use. Test with representative agent and supervisor accounts.
5. Build sequence
- Confirm case lifecycle and required fields.
- Review existing Case views, forms, relationships, and choices.
- Create the canvas app and add Dataverse connections.
- Implement browse, detail, and update experiences.
- Add validation, error handling, and role-based testing.
Next: build the case browse gallery with useful filters and a delegable query.
