Forum Discussion
Direct Lake Model - Implicit measures vanished
- 1 year ago
Hi Plecky
The issue of implicit measures disappearing in Power BI when using Direct Lake mode is likely due to recent changes in Power BI behavior or semantic model settings. Here are some potential reasons and solutions:Possible Causes & Fixes:
1. Direct Lake Mode and Aggregations Limitation
-
Implicit measures (auto sum, count, avg, etc.) are not always available in Direct Lake mode if Power BI detects potential performance issues.
-
Fix: Try switching the storage mode of the table to "Import" or "Dual" instead of Direct Lake (if possible).
2. Column Data Type & Aggregation Settings
-
Check if the "Summarize By" property of your numeric column (
Cost) has changed:-
Go to Power BI Desktop → Model View.
-
Click on the
Costcolumn. -
Look for "Summarize By" in the properties pane.
-
Ensure it is set to Sum (or another aggregate function) instead of "Do not summarize."
-
3. Power BI Desktop Update Issue
-
A recent Power BI update may have changed behavior for implicit measures in Direct Lake models.
-
Fix: Try rolling back to an older version of Power BI Desktop to see if the issue persists. You can download older versions from the Power BI archive.
4. Power BI Service Configuration Issue
-
If the model is published to Power BI Service, check the settings:
-
Go to Power BI Service → Open the Semantic Model.
-
Click on Model Settings.
-
Ensure that "Allow Implicit Measures" is enabled.
-
5. Workspace or Fabric Configuration Change
-
If your Fabric environment was updated, there may be default settings affecting implicit measures.
-
Fix: Try creating a new test model with Direct Lake and see if implicit measures work there.
Next Steps
-
Check "Summarize By" settings in Model View.
-
Ensure Direct Lake limitations are not affecting implicit measures.
-
Try rolling back Power BI Desktop if this issue appeared after an update.
-
Check settings in Power BI Service or Fabric Admin Portal.
Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!
-
Hi Plecky
The issue of implicit measures disappearing in Power BI when using Direct Lake mode is likely due to recent changes in Power BI behavior or semantic model settings. Here are some potential reasons and solutions:
Possible Causes & Fixes:
1. Direct Lake Mode and Aggregations Limitation
-
Implicit measures (auto sum, count, avg, etc.) are not always available in Direct Lake mode if Power BI detects potential performance issues.
-
Fix: Try switching the storage mode of the table to "Import" or "Dual" instead of Direct Lake (if possible).
2. Column Data Type & Aggregation Settings
-
Check if the "Summarize By" property of your numeric column (
Cost) has changed:-
Go to Power BI Desktop → Model View.
-
Click on the
Costcolumn. -
Look for "Summarize By" in the properties pane.
-
Ensure it is set to Sum (or another aggregate function) instead of "Do not summarize."
-
3. Power BI Desktop Update Issue
-
A recent Power BI update may have changed behavior for implicit measures in Direct Lake models.
-
Fix: Try rolling back to an older version of Power BI Desktop to see if the issue persists. You can download older versions from the Power BI archive.
4. Power BI Service Configuration Issue
-
If the model is published to Power BI Service, check the settings:
-
Go to Power BI Service → Open the Semantic Model.
-
Click on Model Settings.
-
Ensure that "Allow Implicit Measures" is enabled.
-
5. Workspace or Fabric Configuration Change
-
If your Fabric environment was updated, there may be default settings affecting implicit measures.
-
Fix: Try creating a new test model with Direct Lake and see if implicit measures work there.
Next Steps
-
Check "Summarize By" settings in Model View.
-
Ensure Direct Lake limitations are not affecting implicit measures.
-
Try rolling back Power BI Desktop if this issue appeared after an update.
-
Check settings in Power BI Service or Fabric Admin Portal.
Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!
- Plecky1 year agoFrequent Visitor
Hi johnbasha33,
Thanks a lot for your structured response, highly appreciated.
I walked through the different options and here are my findings:
1. Direct Lake Mode and Aggregations Limitation
Fix: Try switching the storage mode of the table to "Import" or "Dual" instead of Direct Lake (if possible).Reponse: Switching Storage Mode is not possible and also not really an option for our use case.
2. Column Data Type & Aggregation Settings
Reponse: As mentioned in the original post, configurations are set properly in the Model and Model View:
Model View Report View 3. Power BI Desktop Update Issue
Fix: Try rolling back to an older version of Power BI Desktop to see if the issue persists. You can download older versions from the Power BI archive.Reponse: We're talking (Big) Enterprise environment, rolling back Software is not an easy option. Anyway, issue is reproducable in the Online Service, hence, I don't think it's related to Desktop version.
4. Power BI Service Configuration Issue
Ensure that "Allow Implicit Measures" is enabled.[PROBLEM SOLVED] Response: Disabling the "Discourage implicit measures" option did the trick, so basically this is the answer needed. Haven't seen it before in any of the options, but it's there 🙂 - Thank you!
5. Workspace or Fabric Configuration Change
Fix: Try creating a new test model with Direct Lake and see if implicit measures work there.Reponse: Creating a new model from scratch would actually solve the issue and bring back implicit measures. However, I hope this could be avoided due to tremendous re-creation effort.
- Plecky1 year agoFrequent Visitor
And maybe to add to this: I do have another Semantic Model based on the one with Direct Lake Mode and here the Implicit Measures work fine again, so it must be a specific configuration topic.
I realized it has huge impact, because I can't even drag such fields into "Value" data fields section anymore. It's crazy because I have existing reports with matrix visuals where it is working, but trying to replicate exact same visual isn't working anymore.
- Anonymous1 year agoNot applicable
Hi Plecky,
Just following up to your previous message, I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.Best Regards,
Hammad.
Community Support Team