Issue with Usage metrics - OLEDB or ODBC error

[pkn7]

Hi,

I have created a custom usage metrics report connecting to both new and old usage metrics model. i want to show the dept info for the users of the reports. so when i try to combine a excel file(which has user dept info) to this model the report breaks always. i have created the relationship of the excel file with the other usage metrics tables which are connected in direct query mode. but everytime when i try to visualize the report is breaking.

Thank you,

Priyanga

[Anonymous]

Hi, @pkn7 

This problem is usually caused by some data in your Power query not meeting your query steps or your Excel version being too low.

Make sure you are using the latest version of Excel or you need to install the corresponding ODBC driver:

Power Query Excel connector - Power Query | Microsoft Learn

Best Regards

Jianpeng Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[123abc]

Here are a few steps you can try to troubleshoot and resolve the issue:

1. Check Data Types and Relationships: Ensure that the data types of the columns you’re using to create relationships are compatible. Sometimes, mismatched data types can cause errors.

2. Import Mode for Excel Data: Instead of using DirectQuery for the Excel file, try importing the Excel data into your model. This can sometimes resolve issues related to combining different data sources.

3. Query Dependencies: Review the query dependencies in your model. Ensure that there are no circular dependencies or complex relationships that might be causing the report to break.

4. Data Refresh: Make sure that all data sources are refreshed and up-to-date. Sometimes, stale data can cause unexpected errors.

5. Error Details: Look at the detailed error message when the report breaks. This can provide clues about what might be going wrong. Specifically, check for any OLEDB or ODBC error codes that can be further investigated.

6. Simplify the Model: Try simplifying your model by removing some relationships or tables temporarily to identify if a specific relationship or table is causing the issue.

If these steps don’t resolve the issue, you might want to consider reaching out to the support community or consulting with a Power BI expert who can provide more personalized assistance.

Let me know if you need further help or if there’s anything specific you’d like to dive deeper into!