Free Developer Tool · Apache Ossie / Dosi

Power BI to Apache Ossie Converter

Import offline Power BI model.bim JSON into Apache Ossie. Try a BIM fixture and review native-expression diagnostics before using the generated YAML.

No signup · Sample models included · Offline conversion checks

Conversion Workbench

Source Files1Example

Power BI · Offline BIM (Needs Review)

model.bim

{
  "name": "commerce",
  "compatibilityLevel": 1702,
  "model": {
    "tables": [
      {
        "name": "orders",
        "columns": [
          {
            "name": "id",
            "sourceColumn": "id",
            "dataType": "decimal",
            "isKey": true
          },
          {
            "name": "customer_id",
            "sourceColumn": "customer_id",
            "dataType": "decimal"
          },
          {
            "name": "ordered_at",
            "sourceColumn": "ordered_at",
            "dataType": "dateTime"
          },
          {
            "name": "amount",
            "sourceColumn": "amount",
            "dataType": "decimal"
          }
        ],
        "description": "One row per order",
        "partitions": [
          {
            "name": "orders",
            "mode": "directLake",
            "source": {
              "type": "entity",
              "entityName": "ORDERS",
              "schemaName": "PUBLIC",
              "expressionSource": "DatabaseQuery"
            }
          }
        ],
        "measures": [
          {
            "name": "revenue",
            "expression": "SUM('orders'[amount])",
            "description": "Total order revenue",
            "annotations": [
              {
                "name": "OssieExpressionDialect",
                "value": "ANSI_SQL"
              },
              {
                "name": "OssieExpression",
                "value": "SUM(orders.amount)"
              }
            ]
          },
          {
            "name": "order_count",
            "expression": "DISTINCTCOUNTNOBLANK('orders'[id])",
            "annotations": [
              {
                "name": "OssieExpressionDialect",
                "value": "ANSI_SQL"
              },
              {
                "name": "OssieExpression",
                "value": "COUNT(DISTINCT orders.id)"
              }
            ]
          }
        ]
      },
      {
        "name": "customers",
        "columns": [
          {
            "name": "id",
            "sourceColumn": "id",
            "dataType": "decimal",
            "isKey": true
          },
          {
            "name": "name",
            "sourceColumn": "name",
            "dataType": "string"
          },
          {
            "name": "segment",
            "sourceColumn": "segment",
            "dataType": "string"
          }
        ],
        "description": "Customer attributes",
        "partitions": [
          {
            "name": "customers",
            "mode": "directLake",
            "source": {
              "type": "entity",
              "entityName": "CUSTOMERS",
              "schemaName": "PUBLIC",
              "expressionSource": "DatabaseQuery"
            }
          }
        ]
      }
    ],
    "expressions": [
      {
        "name": "DatabaseQuery",
        "kind": "m",
        "expression": [
          "let",
          "    Source = AzureStorage.DataLake(\"https://onelake.dfs.fabric.microsoft.com/00000000-0000-0000-0000-000000000000/00000000-0000-0000-0000-000000000000\")",
          "in",
          "    Source"
        ]
      }
    ],
    "description": "Orders and customer revenue",
    "relationships": [
      {
        "name": "orders_to_customers",
        "fromTable": "orders",
        "fromColumn": "customer_id",
        "toTable": "customers",
        "toColumn": "id"
      }
    ],
    "culture": "en-US"
  }
}

Source files stay in memory. Upload all referenced files together.

ResultsApache Ossie

Choose a source platform and convert to preview Ossie YAML.

Clicking Convert sends the current source files to Datus servers. No warehouse connection or SQL execution is performed.

What This Converter Does

Convert an offline Power BI / Microsoft Fabric tabular model definition into Apache Ossie. The supplied model.bim fixture deliberately includes native expressions that illustrate the Needs Review workflow.

Source Format

Supported offline BIM JSON. Prepare the model definition separately from credentials; the tool does not unpack an arbitrary PBIX report or retrieve a model from a Fabric workspace.

Generated Output

An Apache Ossie representation and compatibility diagnostics. Review any native DAX, partition or expression notes before using the definition in another runtime.

Conversion Steps

Inspect the offline BIM example or provide your supported model.bim JSON.
Keep Power BI / Microsoft selected as the source and set any available import options.
Convert, open the diagnostics and examine native-expression warnings alongside the generated model.
Download the Ossie definition and independently verify relationships and representative measures.

Review Before Using the Output

No general DAX-to-SQL translation or DAX execution is performed.

A structural representation of a measure does not prove equivalent behavior in the destination runtime.

Continue Exploring

FAQ

Frequently asked questions

Can I upload a Power BI PBIX report?

The supported example and input contract use offline BIM JSON. The browser tool does not unpack an arbitrary PBIX file or log in to a live Power BI or Fabric workspace.

Will DAX be translated into SQL?

No general DAX execution or DAX-to-SQL translation is promised. Inspect native-expression diagnostics and verify the intended semantics in your destination runtime.

Does this publish a model to Microsoft Fabric?

No. The export is an offline BIM JSON definition. Configure any required target metadata and validate the file in your destination workflow; the converter does not publish or refresh a live model.