/

Build a Contact 360 Workspace with Account and Activity Context in Power Apps: Series 10

Power Apps account edit form screenshot

This final part combines the contact profile, parent Account, standard activities, and custom interaction history into a single seller workspace. It is a focused companion experience for Dynamics 365 Sales, not a replacement for the full CRM timeline or security model.

1. Lay out the Contact 360 screen

  • Header: contact name, job title, and status.
  • Account card: parent company name and a link to the Account profile.
  • Contact methods: email and business/mobile phone.
  • Activities: upcoming tasks, calls, and appointments.
  • Interaction history: custom interaction records sorted newest first.

2. Load only what the screen needs

Use the selected Contact record as the screen context. Query related records with delegable filters and keep independent loading operations separate. Avoid collecting entire Dataverse tables into local collections.

Set(varSelectedContact, galContacts.Selected);
Navigate(scrContact360, ScreenTransition.Fade)

// OnVisible: refresh only required sources
Refresh(Contacts);
Refresh(Tasks);
Refresh('Contact Interactions')

3. Add quick actions

  • Send email using the organization’s approved email integration.
  • Create a follow-up task related to the Contact.
  • Open the parent Account workspace.
  • Add an interaction log entry.

4. Preserve Dataverse security

Every related gallery must respect the signed-in user’s Dataverse permissions. Do not expose activities or interaction notes simply because the user can open the Contact screen. Test access using realistic sales roles and ownership scenarios.

5. End-to-end test

  • Open a Contact linked to an Account.
  • Verify the parent Account and contact details.
  • Review related activities and custom interactions.
  • Create a follow-up task and confirm it appears in Dynamics 365.
  • Update the Contact and confirm changes are reflected in CRM.

You now have a compact Contact 360 workspace built on Dataverse. Use the standard Dynamics 365 timeline when complete activity aggregation is required, and keep custom tables focused on business data that standard activities do not capture.