Skip to content

Power BI Naming Conventions

  1. Naming Convention

    1. File Name, e.g. tb_profitability.pbip or tb_profitability.pbix. Specifically:
      1. We prefix each pbix file with the company code
      2. We use lower case
      3. We don't use spaces, but _ instead
      4. We use English for the name
        This is important to understand the source of a problem when we receive a helpdesk notification.
    2. Dataflows also need to be prefixed with the client code, e.g. alki_sales, for the same reason.
    3. We use CamelCase to name Tables, Attributes, e.g. DimCustomer, FactInvoiceLines
    4. We use natural language for measures, Power Query steps
    5. We pre-fix our tables with Dim and Fact, e.g. FactSales
    6. We redundantly include table names in attributes, e.g. CustomerID, CustomerName, etc. in table DimCustomer

  2. Workspace Structure and PBIX Naming Convention

    1. dataset workspace
    2. reports are in separate workspace, pbix is called according to client specs

  3. Language

    1. We use English for Power Query steps, for Tables, for Attributes
    2. We use the target project language for DAX measure names, e.g. Ertrag