Private Preview - features may change without notice
GramSpec
Architecture Spec API Reference Pricing About
Start free

Make the model · 5

A model from a Power BI template

For a company that already runs on Power BI. The modeling in a report they trust comes across, it is not thrown away: drag in the report's template and take every field, or only the fields the report actually uses.

A model from a Power BI template. The report's author saves it as a template and drags it in. The template's tables, relationships and the fields its pages use are read, the used ones are kept, each table's database source is reviewed, and the model is built.YOUR POWER BIGRAMSPECThe templatethe report's model and itspagesWhoever built thereportin Power BI DesktopImport a templateevery field, or only thefields in useRead the templatetables, relationships, thefields each page touchesKeep what is usedand the tables that connectthemReviewwhich database table eachone readsThe modelPower BI's names to read,the database's names forSQL123456 A model from a Power BI template. The report's author saves it as a template and drags it in. The template's tables, relationships and the fields its pages use are read, the used ones are kept, each table's database source is reviewed, and the model is built.GRAMSPECThetemplateWhoeverbuilt thereportin Power BIDesktopImport atemplateRead thetemplateKeep what isusedReviewwhich databasetable each onereadsThe model123456
One flow, worked by rule. Nothing connects to Power BI; the template file is all that crosses.
  1. Whoever built the report saves it as a template. In Power BI Desktop. A template holds the report's model and its pages, and none of its data.
  2. They drag the template in. And choose between every field in the model and only the fields the report uses.
  3. The template is read. Its tables, columns and relationships, and from its pages every field the report touches: in a visual, a filter, a tooltip, a sort or a format.
  4. What the report uses is kept. The tables holding those fields, and the tables that sit between them so they still connect. A calculated column comes with its formula, rewritten into the model's own formula language, and with the columns it depends on.
  5. Someone reviews where each table really lives. Each kept table is shown with the database table it reads, and a wrong one is corrected there before the model is built.
  6. The model is built. The names people gave things in Power BI become the words they read, and the database's own names stay underneath for the SQL. A report of what came across, and which fields the report used, comes back as a file.