on
RE:
this is so needed!
RE:
the link below is the originating post on the service forum
RE:
https://community.fabric.microsoft.com/t5/Service/paginated-report-builder-quot-stacked-quot-containers-prevent/m-p/4118667#M243909
RE:
No CRUD that is hilarious Idea originated from here
RE:
Lol nothing has changed just the rebranding well done m$ :}
RE:
Yes! Please! The lack of this capability makes column charts useless for showing time series data that requires any horizontal scrolling.
RE:
Absolutely! I've been needing this for years!
RE:
Any idea if this can be added ?? Its really difficult to manage that without data entity.
RE:
This is extremely important in any database technology.
RE:
The case status will not be marked as "resolved" or "mitigated," nor will it be closed. Instead, it will remain under your ownership but be placed in a designated bucket, panel, window, or box where it will not contribute to your active backlog count. This approach ensures that while the case is still under your responsibility, it does not impact your backlog metrics.If you anticipate being out of the office (OOF) or if another engineer needs to oversee the case while awaiting further customer action, you can coordinate with the Technical Advisor (TA) for reassignment. This means that the case will remain open but will be managed in such a way that it does not artificially inflate your backlog.The ultimate goal is not merely to save time but to ensure that our metrics accurately reflect the cases that are actively being worked on. By excluding cases that are merely pending customer input from the backlog count, we maintain a clearer and more accurate representation of our workload.