Free Developer Tool · Apache Ossie / Dosi

Apache Ossie to Power BI Converter

Export Apache Ossie definitions as offline Power BI / Microsoft Fabric BIM JSON. Review target metadata, inspect generated files and validate the model.

No signup · Sample models included · Offline conversion checks

Conversion Workbench

Source Files1Example

Omni Sales · ANSI_SQL

omni_sales.yml

# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied.  See the License for the
# specific language governing permissions and limitations
# under the License.

# yaml-language-server: $schema=../../../../core-spec/ossie-schema.json
#
# Fixture A -- all-native round-trip (Ossie -> Omni -> Ossie).
# Star schema; every construct maps to a native Omni slot. Documented
# normalizations on the Ossie -> Omni -> Ossie trip: relationship names are
# regenerated (`<from>_to_<to>`), and unique_keys that merely restate the
# primary key are absorbed by it.

version: "0.2.0.dev0"

name: sales
description: Sales orders with customer attributes
ai_context:
  instructions: "Use this model for order analysis."
datasets:
  - name: orders            # fact: no incoming relationship -> topic base_view
    source: samples.tpch.orders
    primary_key: [o_orderkey]
    description: One row per order
    fields:
      - name: o_orderkey
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_orderkey
        description: Order identifier
      - name: o_custkey
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_custkey
      - name: o_orderdate
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_orderdate
        label: Order Date
        dimension:
          is_time: true
        ai_context:
          synonyms: [order date, date]
      - name: o_totalprice
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_totalprice
  - name: customer
    source: samples.tpch.customer
    primary_key: [c_custkey]
    fields:
      - name: c_custkey
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: c_custkey
      - name: c_name
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: c_name
        description: Customer name
relationships:
  - name: orders_to_customer
    from: orders
    to: customer
    from_columns: [o_custkey]
    to_columns: [c_custkey]
metrics:
  - name: total_revenue
    expression:
      dialects:
        - dialect: ANSI_SQL
          expression: SUM(orders.o_totalprice)
    description: Total order revenue
    ai_context:
      synonyms: [revenue, sales]
  - name: order_count
    expression:
      dialects:
        - dialect: ANSI_SQL
          expression: COUNT(*)
    description: Number of orders

Source files stay in memory. Upload all referenced files together.View Original Example

Results

Choose a target and convert to preview temporary files.

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

What This Converter Does

Generate an offline Power BI / Microsoft Fabric BIM model from Apache Ossie definitions. This export workflow creates model files for review; it does not publish a semantic model into a Fabric workspace.

Source Format

Apache Ossie YAML. Use the supplied sales model or upload your own compatible definition, then review its datasets, relationships and metrics.

Generated Output

Offline BIM JSON for the Microsoft Power BI / Fabric target. Required target metadata is supplied by the deployed catalog and must be completed before conversion.

Conversion Steps

Inspect the Ossie sales fixture or upload the model you want to export.
Keep the Power BI / Fabric destination and fill in required metadata shown by the workbench.
Convert and inspect the generated BIM structure, native expressions and diagnostics.
Download the result, validate it in your destination workflow and compare representative Power BI measures.

Review Before Using the Output

The output is not a PBIX report, a live workspace connection or a deployed Fabric item.

Validate target metadata and measure behavior. Conversion does not execute DAX, refresh a model or prove native expression equivalence.

Continue Exploring

FAQ

Frequently asked questions

What format does the Ossie-to-Power-BI converter export?

The Microsoft Power BI / Fabric target exports offline BIM JSON. It does not create a PBIX report or publish a live Fabric semantic model.

Which Power BI target settings are required?

The deployed target catalog supplies the required fields. Fill in the metadata shown by the workbench before converting, then check the generated model against your destination environment.

Does a BIM export prove native measures are equivalent?

No. Review any expression and compatibility diagnostics, validate the BIM definition in your target workflow and compare representative measures. The converter does not execute DAX or refresh the model.