DASH:Gen

Guide

Several CSV files as one Power BI data model

An export rarely comes as one table. Upload the orders with their customers and products, and the project arrives with the relationships between them already built, or with a clear note on which ones it could not find.

Which table is the main one

The file with the most rows becomes the fact table: the orders, the invoice lines, the bookings. The measures are built over it, and every other file is treated as a table that describes it: customers, products, regions. The model stage of the step-by-step route shows which table was chosen and why. When the data has a date column, a calendar table is generated and linked to it; further date columns are linked too, but inactive, because Power BI allows one active path.

How relationships are found

Every column of the main table is scored against every column of the others, and a relationship is made only when one candidate clearly wins:

Star or one flat table

If the lookup tables are joined, the model is a star: one fact table in the middle, the descriptive tables around it, and slicers on a customer or product attribute filter the measures. If you would rather have one wide table, join the files before you upload them; a single file becomes a single-table model with its calendar.

Step by step

  1. Open dashgen.de and drop all files in at once.
  2. Describe the report: which figures, broken down by what.
  3. Press Generate Power BI, or, with an account, go step by step to see the model before the measures are written, and add a join where one is missing.
  4. Open the project in Power BI Desktop and check the model view.

How each file's rows travel with the project, embedded or linked, is in the Excel to Power BI guide.

Questions

How many CSV files can DASH:Gen combine into one Power BI report?

Without an account, up to five files for one Power BI report, and their rows have to fit inside the project together. With an account the number depends on the plan; the price list has it.

What does DASH:Gen do with a file it cannot join?

DASH:Gen keeps it in the model without a relationship, and the model stage lists it under Not linked to the main table, with the reason. Nothing is guessed.

Can I tell DASH:Gen which columns to join on?

Yes, with an account, in the model stage of the step-by-step route. A join you state is kept even where inference found nothing, and a second join between the same two tables is kept inactive.

Try it without an account

Three HTML dashboards, one Power BI report and one Apache Superset bundle a day need no sign-up and no card. No file to hand? Pick Sales under the drop zone.

Open DASH:Gen