Forum Discussion
Heavy User in Fabric Capacity Metric App
- Anonymous8 months ago
Hi TarunSingh84060,
Thanks for your detailed explanation.
The Timepoint Interactive Detail table is designed to return data only when a single 30-second timepoint is selected. If multiple timepoints are selected, or if no timepoint is selected, it will not populate any values. Because of this behavior, it is not possible to retrieve or export user-level data for a range such as the last 7 days directly from that table.
At present, there is no supported way within the default Capacity Metrics semantic model to pull interactive user details across multiple timepoints in one go. The drillthrough page is intentionally scoped to a single timepoint context. So you are not missing anything this is a limitation of the current design of the Capacity Metrics app model.
Please let us know if you need any further clarification.
Regards,
Community Support Team
Thanks for your response. I have tried creating measures in PBI as I have build access to its semantic model however what I have observed is the timepoint interactive table doesn't populate any values till the time a single timepoint is not selected. Even if I take timepoint column in a slicer it is by default at a single selection (we cannot change it to multi select). I have tried pulling columns in a table visual and the visual is al blank till the time I dont select any one particular timepoint. Even I have created a normal aggregation measure and even that is not working.
Apart from timepoint tables I dont see Users listed in any other table. Only tabble is Items which has user but doesn't have relationship with other tables.
Any suggestions...
- Anonymous8 months agoNot applicable
Hi TarunSingh84060,
Thank you for reaching out to the Microsoft fabric community forum.
The Timepoint Interactive Detail table works only when one single timepoint is selected. If no timepoint is selected, or if you try to look at multiple timepoints, the visuals and measures will stay blank.Currently, the built-in semantic model does not support last 7 days or multi-timepoint user analysis. Also, the Items table is not related to the timepoint tables, so it cannot be used to get user data across time.
For analyzing heavy users over a time range, you will need to export the capacity metrics data and build your own custom report/model. This limitation cannot be changed inside the default app.
Hope this helps clarify.
Kindly refer to the below documentation links for better understanding:
Understand the metrics app timepoint page - Microsoft Fabric | Microsoft Learn
Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.
Regards,
Community Support Team.- TarunSingh840608 months agoRegular Visitor
Hi v-hjannapu, thanks for your response. I am aligned with you on the limitation of the model. However can you help me out in understanding on how can i export the data for last 7 days with user details as it works on 30 second timepoints. We have a drillthrough table for Interactive timepoint details giving us the user level information which however is on a 30 second timepoint. there will be lot of manual effort to drillthrough with each timepoint to get the data. Is there any other way? Am i missing anything here?
- Anonymous8 months agoNot applicable
Hi TarunSingh84060,
Thanks for your detailed explanation.
The Timepoint Interactive Detail table is designed to return data only when a single 30-second timepoint is selected. If multiple timepoints are selected, or if no timepoint is selected, it will not populate any values. Because of this behavior, it is not possible to retrieve or export user-level data for a range such as the last 7 days directly from that table.
At present, there is no supported way within the default Capacity Metrics semantic model to pull interactive user details across multiple timepoints in one go. The drillthrough page is intentionally scoped to a single timepoint context. So you are not missing anything this is a limitation of the current design of the Capacity Metrics app model.
Please let us know if you need any further clarification.
Regards,
Community Support Team