In Live Connection mode, managing report-level measures faces notable limitations. If a measure name duplicates one in the dataset, it may cause an error because automatic renaming or suffix suggestions are not currently supported. Additionally, report-level measures cannot be cleanly organized or grouped. Users cannot create new tables or folder structures to reduce naming conflicts.
Report-level measures also remain invisible to the upstream semantic model in most scenarios. This separation can occasionally lead to missing or broken references when a dataset is reused across multiple reports.
Introducing a dedicated organizing container (e.g. a virtual table or folder) for report-level measures and providing smarter naming assistance (such as suffix suggestions on duplicate names) would improve consistency, reduce developer friction, and make Live Connection scenarios more robust.
frithjof_v
on:
Monitoring hub show detailed error logs