Submitted on10-21-201911:50 AMSubmitted byLucianon10-21-201911:50 AM
Hello, I have a table similar to this one I need a comparison table ("1 vs 1") with 2 columns based on Year column, using two slicers for years. So, I've created 2 tables for each slicer based on the year column using this thread: Re: Two slicer on same column FilterTBL-Base = DISTINCT('DataTable'[Year]) FilterTBL-CompareTo = DISTINCT('DataTable'[Year]) And for each "filter table" I have created the corresponding measure to know the selected value: SelectedYear-Base = SELECTEDVALUE('FilterTBL-Base'[Year]) and SelectedYear-CompareTo = SELECTEDVALUE('FilterTBL-CompareTo'[Year]) Now I am able to calculate the "base total" and the "total to compare to" in my data table using the following measures: TotalBase = SUMX(FILTER('DataTable','DataTable'[Year]=[SelectedYear-Base]),'DataTable'[Cost]) and TotalCompareTo = SUMX(FILTER('DataTable','DataTable'[Year]=[SelectedYear-CompareTo]),'DataTable'[Cost]) So the entire structure looks like this: The calculation works as expected: The only problem it bothers me, is that the final table should have the column names based on the slicer selections. In picture above TotalBase should display "FY_2010" and the TotalCompareTo should display "FY_2011". I could obtain this by manually renaming the measured used in the value field, but if the user select other options in the slicer I have to rename the fields again. As I could rename the field manually, could you consider a way to "set its name" by another measure value (ex. SelectedYear-Base)? For the moment the only "workaround" is an card visual with the same font/size as the other colum titles from the table but loosing in this way the "focus mode" for that table, sorting etc... Kind Regards, Lucian
... View more
Submitted on07-30-202006:29 AMSubmitted bySaVeron07-30-202006:29 AM
This option is possible in QlickSense, but unfortunately not in Power BI. Like in QlickSense you could then work with a loose slicer: the user can show/hide the columns of his choice. So sad to see that this is still not possible in Power BI.
... View more
For conditional formatting in the Table visualization (perhaps others), when using Greater than or Equal to within the Format by Rules option, the current desktop Power BI version requires an endpoint on the range (either less than, or less than or equal to). This may require the user to enter an arbitrary high number so that all possible values Greater than the the specified value be addressed. In other words, please remove the requirement that the Less Than value be provided when the Greater Than (or Greater Than or Equal To) option is selected for the rule. Thanks.
... View more