This series extends the sales workspace with contact management. The app uses the standard Dataverse Contact and Account tables, allowing sellers to review people, understand their company relationship, and record follow-up activity while Dynamics 365 Sales remains the system of record.
1. Define the user journey
- Browse contacts by name, email, or related account.
- Open a contact profile and view its parent account.
- Create or update contact details.
- Review related phone calls, appointments, and tasks.
- Launch a follow-up action from the contact profile.
2. Use standard Dataverse tables
Use Contact for person details and Account for the organization. The standard Contact table includes a relationship to its parent customer, which can refer to an Account or, where configured, another supported customer record. Activities use the Dataverse activity model; tasks, phone calls, and appointments have their own tables and relationships.
3. Plan screens
- Contacts: searchable gallery with name, job title, email, and company.
- Contact Profile: contact details and parent account.
- Edit Contact: typed form cards for text, email, phone, and lookup columns.
- Activities: related tasks, calls, and appointments.
4. Choose the right integration boundary
Use Power Fx for screen behavior and straightforward record editing. Use Dataverse relationships for contact-to-account association. If an operation needs special business rules, approvals, or multi-record processing, put it in a secured cloud flow or server-side Dataverse extension.
5. Security and validation
Test contact and account privileges with representative users. Verify that users can only see and edit records allowed by their Dataverse roles and ownership access. Confirm your environment’s relationship schema, column security, and customizations before reusing formulas.
Microsoft’s Power Apps canvas app documentation provides guidance for building apps connected to Dataverse.
