Skip to main content

How to Configure Dashpivot Data in Power Query Excel/Power BI via Flowsite

Learn how to configure Dashpivot data for clean transformation and error-free reporting using Power Query in Excel or Power BI via Flowsite

Written by Nina Yang

This guide explains how to load, clean, and understand data exported from Dashpivot using Power Query Editor. The data originates from Dashpivot forms, is synced to Flowsite, and then exported as CSV file for reporting.

It’s designed for all experience levels and helps you prepare Flowsite data for analysis. By following this process, you can prevent common data errors, structure your dataset correctly, and ensure reliable transformations.

Prerequisites

Before you begin make sure you have the following:

  • Plan: All Plan Types

  • Skills Required: Data transformation using Power Query

  • Device Type: Computer/Browser

  • Subscription: Flowsite, Dashpivot, Excel/Power BI

Step 1 — Connect your Flowsite data source

  1. Open Power Query Editor from Excel/Power BI

  2. In the Connect to data source window. Enter your username and password from Flowsite.

  3. Once connected, your data loads automatically.

Step 2 — Use the first row as column headers

  1. In Excel/Power BI, go to Data → Get Data → Launch Power Query Editor.

  2. In Power Query Editor, click Use First Row as Headers so your column names display correctly.

  3. In the Query Settings pane on the right, remove Changed Type in Applied Steps.
    (This prevents errors caused by dashes in numeric or date fields.)

Step 3 — Understand your data structure

Data recorded in Dashpivot forms determines how it appears in Flowsite exports.

Each form has a unique Form ID (see the Form ID column).

  • Repeated rows: A form with multiple entries/rows will repeat top-level fields (expected behavior).

  • Single row: Forms without tables (or with one entry) appear once.

If a Form ID repeats, it contains multiple entries (rows), not just table data.

Note: Multiple rows can come from table fields, photos, or any multi-entry field—not just tables.

Step 4 — Fix common errors before changing types

For number or date columns:
Flowsite uses a dash () or (blank) for blank values. Replace these before converting column types.

If a field (e.g. date, time, or number) is not required in Dashpivot and left blank, it will appear as a dash in Flowsite exports. This can cause errors during type conversion.

To fix this:

  1. Select the column.

  2. Use the column filter to identify blanks or dash (-) values.

  3. Go to Transform → Replace Values.

  4. Replace or - with blank (null) or 0.

  5. Then set the correct data type.

Tip: It is suggested to reassess how you want to process your data from Dashpivot. Make the field set to required in order not to have blank or dash cells.

How field types export

  • Single-entry field: Repeats across all rows in a form

  • Table field: One row per entry

  • Signature field: One row per form (use Fill Down if needed)

  • Photo field: One row per photo (includes location, file path, timestamp)

  • Multiple-entry text: Single row

  • Workflow/status: One value per form

FAQs

Why are rows repeated?
Because the form contains multiple table entries—this is expected.

Why do I get errors when changing column types?
Dashes (—) or (blanks) must be replaced before conversion.

Why does the signature appear only once?
It exports once per form. Replace blanks with null first (Transform → Replace Values, leave “Value to find” empty, set “Replace with” to null), then use Fill Down to apply it to all rows.

How do I count photos in a form?
Count rows with the same Form ID that include a file path.

What data is included with each photo?
File path, GPS coordinates, capture date/time, and tags.


Did this answer your question?