Version 7.9.0 contains code that sets the groundwork for Clio Operate to use Microsoft Fabric by upgrading its analytics platform. This allows Clio Operate to support near real-time reporting (approx. 2-minute data latency). 

You can continue to use reporting as you did before, without changing the Analytics Service from SQL Azure to Microsoft Fabric. 

Possible breaking changes when switching to Fabric

We strongly advise all clients with custom reporting solutions (models, reports, data egress) to test their reporting models and integrations on a non-production environment before switching to Microsoft Fabric in production due to the following breaking changes:

• Deprecated tables in reporting warehouse – the following tables have been deprecated as they were used with legacy features – no usages of these tables were found within existing reporting:
  • dim_kpitargets
  • dim_lifecycle
  • dim_optionsetvaluerelationships
  • dim_sharedotimetargets
  • dim_sharedotyperelationships
  • dim_teamrelationships
  • fact_lifecycle
  • fact_peoplebyday
  • Security.Scope
• The feature no longer supports Power BI application mode – this option has been removed.
• Connection strings in any Power BI semantic models will need to be changed to point to the new data source.

Once Clio Operate is configured to use Fabric

Once Microsoft Fabric is configured, the following features become available:

• Fabric Diagnostic Screen – Monitor performance of analytics builds
  
• UPN Passing – Enables row-level filtering using effective usernames
• DirectQuery Support – Real-time data querying for Power BI models
  See Power BI DirectQuery overview
• External Data Sharing – Allows clients with Fabric capacity to connect to their own Data Lakes or Warehouses

Updated Out-of-the-Box Reports

All standard Power BI reports will automatically use the new Fabric data source and benefit from near real-time updates.

Custom Reports

Case Sensitivity

As part of the analytics platform upgrade, custom Power BI reports and any SQL queries written directly against the Azure SQL database must now adhere to case sensitivity rules:

• Table names are now lowercase (e.g. dim_sharedo)
• Column names follow camelCase (e.g. sharedoId, sharedoTypeDisplayName)

Please update any queries to match this format to ensure compatibility.

DirectQuery Mode

To enable near real-time data access, custom Power BI reports should use DirectQuery mode.

Note: You cannot convert an existing Import mode query to DirectQuery. Instead:

• Copy the SQL from the original query
• Create a new query
• Paste the SQL and select DirectQuery as the Data Connectivity Mode
  

Updated Connection Strings

You will receive new connection details for each environment that can be added to your report. To apply these in Power BI:

• Open Transform Data > Manage Parameters
• Update the Server and Database parameters with the new values
  
• Refresh the report — you will be prompted to authenticate using the new credentials

If you are not using parameters to define your data source connection:

• Go to Transform Data > Data Source Settings
• Update the connection details directly

Deployment Recommendations

Once the report has been refreshed successfully:

• Deploy it to a Power BI workspace
• In the workspace, review the semantic model settings
  • Under Gateway and Cloud Connections, create and map the required connection
    
• It is recommended to test all reports in a non-production environment before promoting them

Licensing Implications

• Existing A SKU embedded capacities will still work with the new SQL connection details.
• An F SKU must be purchased to enable external data sharing with your tenant.