Exporting Records from Power Apps Canvas to Excel: The Complete Guide

The Problem

You’ve built a beautiful canvas app backed by Dataverse. Your users can filter, sort, and search records perfectly.

Then someone asks:

“Can I export what I see to Excel?”

Unlike Model-Driven Apps, canvas apps don’t have a built-in Export to Excel button. You need to build this yourself.

In this guide, we’ll walk through 5 different methods — each with step-by-step instructions, honest pros, and honest cons.

Before We Start

Every method in this guide assumes:

• Your data lives in Dataverse tables
• Your gallery already has filters and sorting applied
• Your gallery’s Items property looks something like this:

SortByColumns(
    Filter(
        Accounts,
        Status = drpStatus.Selected.Value,
        StartsWith(Name, txtSearch.Text)
    ),
    "revenue",
    If(SortDescending, SortOrder.Descending, SortOrder.Ascending)
)

Let’s dive in! 🚀

Method 1: Collection → Power Automate Loop → Excel

This is the most common approach you’ll find online. Collect your filtered records, send them as JSON, and use Power Automate to write each row into an Excel table.

Step 1: Collect the Filtered Records

Add an Export button to your screen. Set its OnSelect to:

ClearCollect(
    colExportData,
    ForAll(
        Gallery1.AllItems,
        {
            AccountName: ThisRecord.Name,
            Revenue: ThisRecord.Revenue,
            Status: ThisRecord.Status,
            City: ThisRecord.Address1_City
        }
    )
);

Why ForAll? It captures exactly what the user sees and flattens lookups/choices into simple text values.

Step 2: Convert to JSON

Add this after the ClearCollect:

Set(varJSONExport, JSON(colExportData, JSONFormat.IndentFour));

Step 3: Create the Power Automate Flow

1. Go to Power Automate → Create → Instant cloud flow
2. Set the trigger to PowerApps (V2)
3. Add an input of type Text called ExportJSON
4. Add a Parse JSON action
   • Content: triggerBody()['text']
   • Schema: Generate from a sample JSON array of your columns
5. Add an Apply to each loop over the parsed JSON body
6. Inside the loop add Excel Online (Business) → Add a row into a table
   • Point to a pre-created Excel file in SharePoint
   • Map each column to the parsed JSON fields
7. Add a Respond to a PowerApp or flow action returning the file URL

Step 4: Call the Flow from Power Apps

Set(varFileURL, ExportToExcelFlow.Run(varJSONExport));
Launch(varFileURL);
Notify("Export complete!", NotificationType.Success);

Step 5: Pre-Create the Excel Template

1. Go to your SharePoint document library
2. Create a blank .xlsx file
3. Add a Table with headers matching your columns — Account Name, Revenue, Status, City
4. Save the file — the flow will append rows to this table

Pros

• ✅ Exports exactly what the user sees
• ✅ Full control over which columns are exported
• ✅ Works with complex filter logic
• ✅ User-triggered and intuitive

Cons

• ❌ Apply to each is painfully slow for 500+ rows
• ❌ JSON payload from Power Apps has a ~2 MB limit
• ❌ Requires a Power Automate license
• ❌ Excel template must be pre-created with correct headers

Method 2: JSON + Office Script (No Loops)

This method eliminates the slow loop from Method 1. Instead of writing row-by-row, an Office Script writes all rows at once.

Step 1: Collect and Convert to JSON

Same as Method 1 Steps 1 and 2:

ClearCollect(
    colExportData,
    ForAll(
        Gallery1.AllItems,
        {
            AccountName: ThisRecord.Name,
            Revenue: ThisRecord.Revenue,
            Status: ThisRecord.Status
        }
    )
);
Set(varJSON, JSON(colExportData, JSONFormat.IndentFour));

Step 2: Create the Office Script

In Excel Online, go to Automate → New Script and paste:

function main(workbook: ExcelScript.Workbook, jsonData: string) {
    let data: Array<{
        AccountName: string;
        Revenue: number;
        Status: string;
    }> = JSON.parse(jsonData);

    let sheet = workbook.getActiveWorksheet();

    // Clear previous data
    sheet.getUsedRange()?.clear();

    // Write headers
    let headers = ["Account Name", "Revenue", "Status"];
    sheet.getRangeByIndexes(0, 0, 1, headers.length)
         .setValues([headers]);

    // Write ALL rows at once
    let rows = data.map((item) => [
        item.AccountName,
        item.Revenue,
        item.Status
    ]);

    if (rows.length > 0) {
        sheet.getRangeByIndexes(1, 0, rows.length, headers.length)
             .setValues(rows);
    }

    // Format as table
    let range = sheet.getRangeByIndexes(
        0, 0, rows.length + 1, headers.length
    );
    sheet.addTable(range, true);
}

Save the script.

Step 3: Build the Power Automate Flow

1. Trigger: PowerApps (V2) → Input: ExportJSON (Text)
2. Add a Run script action (Excel Online Business)
   • Location: Your SharePoint site
   • Document Library: Select the library
   • File: Select your Excel workbook
   • Script: Select the script you created
   • ScriptParameters/jsonData: triggerBody()['text']
3. Add a Respond to a PowerApp or flow action returning the file URL

Step 4: Call the Flow

Set(varFileURL, ExportViaOfficeScript.Run(varJSON));
Launch(varFileURL);

Pros

• ✅ Much faster than Method 1 — all rows written at once
• ✅ Clean Excel output with formatted table
• ✅ Can handle 2,000–5,000 rows comfortably
• ✅ No slow Apply to each loops

Cons

• ❌ Requires Office Scripts (needs Microsoft 365 Business Standard or higher)
• ❌ Still subject to the ~2 MB JSON payload limit
• ❌ Office Scripts not available in all tenants (GCC, etc.)
• ❌ Slightly more complex setup

Method 3: Pass Filter Criteria → Power Automate Queries Dataverse

Instead of sending data to the flow, you send filter criteria. Power Automate queries Dataverse directly, completely bypassing the 2,000-row delegation limit.

Step 1: Capture the User’s Filter Selections

// On drpStatus.OnChange
Set(varFilterStatus, drpStatus.Selected.Value);

// On sort toggle
Set(varSortColumn, "revenue");
Set(varSortOrder, "desc");

Step 2: Create the Power Automate Flow

1. Trigger: PowerApps (V2) with these inputs:

   • FilterStatus (Text)
   • SortColumn (Text)
   • SortOrder (Text)
   • SearchText (Text)

2. Add a List rows action (Dataverse):

   • Table: Accounts
   • Filter rows:

   statuscode eq '@{triggerBody()['text_1']}' and startswith(name, '@{triggerBody()['text_4']}')
   

   • Sort by:

   @{triggerBody()['text_2']} @{triggerBody()['text_3']}
   

   • Row count: 5000

3. Add a Create CSV table action (Data Operations):

   • From: value output of the List rows action
   • Columns: Custom — map only the columns you need

4. Add a Create file action (SharePoint):

   • File Name: Export_@{utcNow()}.csv
   • File Content: Output of Create CSV table

5. (Optional) Add a Convert file action (OneDrive for Business):

   • Convert the .csv to .xlsx if needed

6. Add a Respond to a PowerApp or flow action → Return the file URL

Step 3: Call the Flow from Power Apps

Set(
    varExportLink,
    ExportFromDataverse.Run(
        varFilterStatus,
        varSortColumn,
        varSortOrder,
        txtSearch.Text
    )
);
Launch(varExportLink);
Notify("Your export is ready!", NotificationType.Success);

Pros

• ✅ No delegation limits — Power Automate queries Dataverse server-side
• ✅ Can handle tens of thousands of rows
• ✅ No large payloads sent from Power Apps
• ✅ Fast execution

Cons

• ❌ Must rebuild filter logic as OData — can drift from app logic
• ❌ Complex filters (nested OR/AND) are harder in OData
• ❌ Sorting on lookup fields is tricky
• ❌ User waits 15–60 seconds for the flow to complete

Method 4: Launch a Dataverse View URL

If your Dataverse table has saved views that match common filter combinations, you can skip Power Automate entirely and launch the built-in export.

Step 1: Create a Saved View in Dataverse

1. Go to make.powerapps.com
2. Navigate to Tables → Open your table
3. Click Views → + New view
4. Add the columns you want
5. Apply your filters
6. Save the view
7. Copy the View ID from the URL

Step 2: Construct the Export URL

Dataverse supports a direct export URL pattern:

https://{org}.crm.dynamics.com/_grid/print/export_to_excel.aspx?entity={table_logical_name}&viewid={view_guid}&viewtype=1039

Step 3: Add a Launch Button in Power Apps

Launch(
    "https://yourorg.crm.dynamics.com/" &
    "_grid/print/export_to_excel.aspx?" &
    "entity=account&" &
    "viewid=%7bYOUR-VIEW-GUID%7d&" &
    "viewtype=1039",
    {},
    LaunchTarget.New
)

Step 4: (Optional) Switch Views Dynamically

If you pre-create multiple views for common filter states:

Launch(
    "https://yourorg.crm.dynamics.com/" &
    "_grid/print/export_to_excel.aspx?" &
    "entity=account&viewid=" &
    If(
        drpStatus.Selected.Value = "Active",
        "%7bACTIVE-VIEW-GUID%7d",
        "%7bINACTIVE-VIEW-GUID%7d"
    ) &
    "&viewtype=1039",
    {},
    LaunchTarget.New
)

Pros

• ✅ Zero Power Automate needed — no premium license required
• ✅ Very simple to implement
• ✅ Handles large datasets natively
• ✅ Produces a proper .xlsx file

Cons

• ❌ Filters are static — tied to pre-created views
• ❌ Not “what you see is what you export”
• ❌ User needs Dataverse/Dynamics license with view access
• ❌ URL format can break with platform updates
• ❌ Limited to the views you pre-create

Method 5: CSV via Concat() + Power Automate File Save

This is the lightest-weight method. Build the entire CSV string in Power Apps using Concat(), then send it to a dead-simple flow that saves it as a file.

Step 1: Build the CSV String

On your Export button’s OnSelect:

Set(
    varCSV,
    "Account Name,Revenue,Status,City" & Char(13) & Char(10) &
    Concat(
        SortByColumns(
            Filter(
                Accounts,
                Status = drpStatus.Selected.Value,
                StartsWith(Name, txtSearch.Text)
            ),
            "revenue",
            If(
                SortDescending,
                SortOrder.Descending,
                SortOrder.Ascending
            )
        ),
        """" & Name & """" & "," &
        Text(Revenue) & "," &
        """" & Text(Status) & """" & "," &
        """" & Address1_City & """",
        Char(13) & Char(10)
    )
);

Important: Wrap text values in escaped double quotes ("""") to handle commas inside field values.

Step 2: Create a Simple Flow

1. Trigger: PowerApps (V2) → Input: CSVContent (Text)
2. Add a Create file action (SharePoint):
   • Folder Path: /Shared Documents/Exports
   • File Name: Export_@{utcNow()}.csv
   • File Content: triggerBody()['text']
3. (Optional) Add a Convert file action (OneDrive):
   • Convert .csv → .xlsx
4. Add a Respond to a PowerApp or flow action → Return the file URL

Step 3: Call the Flow and Open the File

Set(varFileLink, SaveCSVFlow.Run(varCSV));
Launch(varFileLink);
Notify("Export complete!", NotificationType.Success);

Pros

• ✅ Simplest flow — no loops, no scripts, no parsing
• ✅ Exports exactly what the user sees
• ✅ Fast for small-to-medium datasets
• ✅ Low licensing requirements

Cons

• ❌ Concat() is subject to delegation limits (max 2,000 rows)
• ❌ CSV string limited to ~2 MB
• ❌ Must handle special characters manually
• ❌ Produces .csv, not native .xlsx (without conversion step)
• ❌ Complex column types need manual formatting

Comparison Table

Which Method Should You Use?

Here’s a quick decision guide:

• Small dataset + exact filters? → Method 5 (CSV Concat) for simplicity
• Need .xlsx with nice formatting? → Method 2 (Office Scripts)
• Large dataset (10K+ rows)? → Method 3 (OData in Flow)
• Minimal effort, no Power Automate? → Method 4 (Launch View URL)
• Getting started / most tutorials follow this? → Method 1 (Collection + Loop)

Delegation Warning

For Methods 1, 2, and 5, always remember:

1. Set your delegation limit to the max (2,000) under Settings → General → Data row limit
2. If your filtered data might exceed 2,000 rows, use Method 3
3. Show a warning to your users:

If(
    CountRows(colExportData) >= 2000,
    Notify(
        "Warning: Only the first 2,000 records are included.",
        NotificationType.Warning
    )
)

Found this helpful? Share it with your Power Platform community! 🚀