Customer 360 View Assembler

Overview

This on-demand flow assembles a unified "Customer 360" view by fetching account data from Salesforce, pulling related support tickets and billing records from Dataverse, and merging everything into a comprehensive HTML email report. The report is sent to a configurable recipient, giving sales teams and executives a complete view of customer relationships in a single document.

Use Case

Sales teams and executives need a quick, consolidated view of customer relationships across multiple systems. Instead of manually checking Salesforce for account details, then switching to Dataverse for support history and billing records, this flow assembles everything into a single styled HTML email report.

The flow is ideal for teams that:

• One-click customer 360 report — no manual data gathering
• Consolidated view of Salesforce accounts and Dataverse support/billing data
• Professional HTML email format — ready to forward or present
• Fully configurable data sources via env vars — no flow edits to re-target entities
• Parallel data fetches — fast execution even with multiple queries

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Deploying to Another Environment

Import the solution, update the four env vars (Salesforce instance URL, Dataverse support/billing entity names, recipient email), bind the three connection references (Salesforce, Dataverse, Outlook), then turn the flow on.

Change the Salesforce object type

Modify the GetItem action's table parameter to fetch Contacts, Opportunities, or any custom object instead of Accounts.

Change the Dataverse entities

Update flowlibs_Customer360SupportEntity and flowlibs_Customer360BillingEntity env vars to point to your support and billing tables.

Customize the OData filter

The ListRecords actions filter by contains(title/name, accountName). Adjust to use a foreign key lookup if your Dataverse tables have an account ID column.

Add more data sources

Insert additional ListRecords or connector actions between steps 7 and 8, then add a new Compose section and reference it in the final report assembly.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

concat(variables('varSalesforceInstanceUrl'), '/', variables('varAccountId'))

if(equals(length(body('List_Records')?['value']), 0), 'No records found.', concat(length(body('List_Records')?['value']), ' record(s) found.'))