Microsoft Fabric

Integration with Microsoft Fabric is at the same time more simple to setup but also more complicated because of various options how you can bring your data to Microsoft Fabric OneLake. There are generally two options that from UX very close but work completely different - the Data Pipelines or Dataflows Gen2 (using Powerquery).

When choosing data pipelines you can use a copy job to copy data from RevOS Workspace to the OneLake, however we do not recommend you do that. Copy job could be very complicated to setup, simpler way is to use the dataflow instead. This tutorial will show you how you can do it quick and easy. Dataflows Gen2 is very powerful mechanics that can be used also for advanced topics like incremental refresh and historical data with slowly changing dimension type 2 (SCD Type 2).

Select Integrations and click on Enable on PowerBI / Fabric in the RevOS as a source list:

After you enable it you’ll see credentials for your connectivity required for the next steps:

Such as (1) Service account e-mail, (2) Service account key and (3) Dataset name.

Please use Gen 2 dataflow for advanced functionality and better future proof.

After you named your dataflow make sure the default destination is set to your Lakehouse/Warehouse and select the Get data from another source

Then enter the “big query” in the search dialog and select Google Big Query connector.

Then expand the Advanced Options and configure change following default options:

Like on the screenshot:

Then in the Connection credentials please select Service Account Login (1) and use provided Service account email (2) and Service account JSON file content (3) content that you copied from the RevOS:

Then click on Next and then you will see the UI to chose tables, please expand revos-ai project and see your data underneath.

On this dialog you can pick and chose multiple tables you would like to import into your OneLake Lakehouse or Warehouse:

Don’t forget to add the Default Destination for your Dataflow Gen2 to and make sure Queries from the Dataflow are bound to the Destination:

after that you are ready to Publish the dataflow and run it first time. After the first refresh is successful you will be able to see your data in your Lakehouse/Warehouse:

and start building your semantical model:

Data in your RevOS DWH will be updated according to the RevOS configuration, so it make sense to setup the automatic data refresh in the Fabric Lakehouse/Warehouse. For that purpose you could setup an automatic refresh on your dataflow. For that click on ‘…’ on the dataflow and select Settings:

there expand Refresh and configure the refresh schedule:

If you see following error:

reason for that is that PowerBI connector configured to use optional Storage API, however it can be disabled by setting an advanced connector configuration Use Storage Api to false or modify the M code that fetches tables from = GoogleBigQuery.Database() to = GoogleBigQuery.Database([UseStorageApi=true])

Yes, the connectivity you use to fetch data uses a connector build and certified by Microsoft that uses encrypted channels using state of the art and constantly updated encryption mechanisms.

Your data in RevOS is updated at least every 24 hours (or more frequent, according to your configuration and pricing plan). You can configure refresh interval on your dataflow.

See full list of entities in the documentation about the individual connectors, e.g.

Depends on the data, if you import results of your scoring models they can be edited in RevOS. Data that is synced from other systems is exposed as-is to Dataflow. You can however use PowerQuery in Dataflow or DAX in Semantical Model to modify the data during and/or after import to Fabric.

Connection errors can arise due to several issues, such as incorrect API key permissions or firewall settings blocking data transfer. Ensure that your Service Account E-Mail and JSON Keys are correctly configured and you can access RevOS platform. If issues persist, reach out to support at revos.ai and we will help you.