Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
I had made a live connection to a cube and need a field parameter functionality. So, I changed the connection from live to Direct query. I made the field parameters and created a slicer and table with my measures. When I published this report to service, I'm getting a pop-up like the below and when I check on the service it says "Couldn't load the data for this visual.
Are field parameters allowed in Direct Query ? Please help me on this
Regards,
Prabha
Hi @Prabha45
Based on the screenshot you provided, it indicates that the dataset contains calculated tables or columns that reference remote tables.
This is a known limitation when using the DirectQuery schema, especially for calculated tables or columns that rely on Analysis Services connections.
You can try the following ways to solve the problem:
Use the Analysis Services connector to import the data in instead of using DirectQuery.
Check for calculated tables or columns in your dataset that depend on remote tables and consider removing them or changing their dependencies.
See the specific limitations of calculated tables and columns in power bi service and make changes to your dataset accordingly.
Solved: Error message on publishing: "This dataset contain... - Microsoft Fabric Community
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the reply.
The calculated table automatically gets created when we created field parameters.
The data is huge which will not support import mode.
Power BI don't allow to create field paramters in live connection. So, I changed it to direct query and created field parameters. When I publish I get the above error and I'm not able to see the data in service.
User | Count |
---|---|
24 | |
21 | |
11 | |
11 | |
10 |
User | Count |
---|---|
50 | |
31 | |
20 | |
18 | |
15 |