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 us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels2 hours agoAdvocate IIINew179Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen3 hours agoAdvocate INew293Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi4 hours agoMicrosoft EmployeeNew18Views6likes0Comments