When creating a line chart using a TOTALYTD measure—where the x-axis shows months and the legend shows years—it can sometimes result in the line for the most recent year rising until the last actual value, and then continuing flat for future dates.
It would be great to have a feature that allows the future portion of the line to be shown as a dashed line.
If there were a calendar table with a flag to distinguish current and future dates, it could be used to split the line visually. However, since those segments would be treated as separate series, the legend would show them as disconnected.
One workaround might be to duplicate the data for the transition month so both flags have values and the lines connect. But that could introduce a many-to-many relationship, which is best avoided.
So ideally, there would be a way to visually connect the current and future lines for the latest year, without creating a many-to-many relationship, and still allow solid lines for current dates and dashed lines for future dates.
Recent ideas
Allow calls of Fabric SQL Database stored procedures from Data Warehouse
It would be great if there were a possibility to call a SQL Database stored procedures directly from a Data Warehouse stored procedures. A use case for this would be e.g. logging activities and even...Vojtech_Dolejsi4 hours agoNew MemberUnder Review2.9KViews13likes3CommentsAllow Data View access for tables sourced from external semantic models
When using DirectQuery for Power BI datasets or semantic model chaining, developers can use remote tables in DAX, relationships, and report visuals, but cannot inspect the underlying rows in Data Vie...kent_lewan14 hours agoNew MemberNew3Views0likes0CommentsDouble cost of licensing for admin users for Fabric Capacity Metrics
For our organization we have specific user accounts for admin work and normal accounts for normal work. We do have an F65 capacity, and for me my normal user account is licensed so I can create. I ...AaronGross14 hours agoNew MemberNew2Views1like0Comments