I am trying to rank my table values as 1,2,3,4,5 etc however when using the RANKX function I have noticed that if my values are the same for example 4 values are 25 then the ranking would be for example 1 for all 4 of those values. But I would want them to be 1,2,3,4 etc.
I have used this DAX measure:
The values are commonly going to be the same for multiple "short descriptions" I am not bothered about the order of the ranking if they are the same. Just making sure the rank rating is in order from 1-15.
Any thoughts?
Thanks
If it is possible in your case to do the Aggregation in Power Query part, you can create your row_number/index there as well. If I guess correct, your value in column Fifth Value is measure and you are doing aggregation with a group by applied on value Short Description. So you are getting Sort Description wise Fifth Value and you need a row number based on values for Fifth Value, right?
If the above is correct, you have to do the Sort Description wise aggregation in Power Query and add the Index there for your filtering purpose in the report.
Related
I am currently creating a pivot table in Quicksight which I am looking to create a Field Well with a series of numbers from 1 to 100. They should be static and not effect the data in the table though. I have managed to do this in PowerBI before using the GENERATESERIES function.
Assuming you have 100 rows in your table, you could create a calculated field that uses denseRank() to assign every row a number from 1 to 100. You would need to make sure you rank on field(s) that do(es) not have duplicates. An index-based rank could work, for example.
I want to calculate % of two columns which are already in %.
I want to calculate formula like
Target achieved= ACTUAL/TARGET
But here is ACTUAL is already a measure/calculated metrics so I'm not able to divide these two columns.
Any help would be appreciated..
Make sure both target and actual are actually numbers and not strings. You can do it in transform data (aka Power Query) part, before data is loaded into the report.
After that you should be able to create the measure you want, e.g. something like that:
UPDATE : What happens if Actual is not a column, but a measure?
If Actual measure is based on the columns in the same table as target you shouldn't have a problem. You cannot combine measure and column in the same formula. Measure is an aggregated field and needs to be grouped by another field (if you are familiar with SQL,think of SUM and GROUP BY). Coming back to your problem, you need to create measure out of "Target" column as well (notice I have in the formula SUM('Table'[Plan]) which makes it a measure). Than you can use both of them in the formula, but of course you need to "group" them by something(e.g. date) otherwise it will just show you a total.
I'm trying to use a previous calculated Measure in a Calculated Column in PBI, but i get the error "expressions that yield variant data-type cannot be used to define calculated columns", how can i fix this? this is my code
Critical_Detrended = 1*(1+[Trend])
Thanks
Calculated columns are static. They are calculated once, when the data is loaded. Their values cannot change. Thus, you can't use something dynamic, like measures, because measures are responsive, they are re-computed when the user selects something, changes the value of a slicer, etc.
The solution in your case is to change your calculated column to be a measure too.
You could take a look for example at Calculated columns and measures in DAX article.
While calculated columns are not responsive to any slicers or filters set on your report, you absolutely can use measures in a calculated column definition so long as you understand how the row context to filter context transition works and don't expect the calculated column to be dynamically responsive.
That said, the error you are getting sounds like [Trend] may output different data types in different situations but a column can only be a single data type. A non-obvious case where this sort of thing happens is when a measure sometimes outputs an integer and other times outputs a decimal type. In a case like that, you can force it to return a decimal type by multiplying by 1.0 or adding 0.0 or similar manner of type coercion. In your case, changing one of the 1 to 1.0 might do the trick if that's indeed the problem.
I'm trying to count days between a date from the column 'completionDate' and today
The table name is 'Incidents (2)'
I have a simuler table called 'incidents' here it's working.
The code:
DaysClosed = DATEDIFF('Incidents (2)'[completionDate].[Dag];TODAY();DAY)
The error i get:
'A single value for variaton 'Dag' for column 'completionDate' in table 'Incidents (2)' cannot be determined. This can happen when a measure formula refers to a column that contains many values without specifying an aggregation such as min, max, count, or sum to get a single result.'
The error you get strongly depends on how you are evaluating your formula, that's why it might work on another table but not on this one. As #JBfreefolks pointed out correctly you are specifying a column where a scalar value is expected. That can work depending on the context you are evaluating your formula over (assuming it is a measure).
For instance, imagine a data-set with 100 rows equally divided into four categories A,B,C,D. When you create a table visual with a row for each category, each row will have 25 underlying records that will be used in any calculation added to this row (either a measure or an aggregate of any value). This means that when using a formula like datediff with a column reference, it will get 25 values for it's second argument where it expects one.
There are several ways to solve the problem depending on your desired result.
Use a measure like MAX like #JBfreefolks suggested to make sure that a single value is selected from multiple values. The measure will still be calculated over a group of records but will summarize it by taking the maximum date.
Make sure the visual you are using has something like an ID in there so it doesn't group, it displays row context. Any measure added to this visual will evaluate in row context as well.
Use a calculated column instead. They are always evaluated in row context first and their values can be aggregated in a visual later on. When using TODAY() , you probably need to refresh your report at least every day to keep the column up to date.
A more complicated way is to use an iterator like SUMX() or AVERAGEX() to force row context evaluation inside of a measure.
Good to see you solved it already, still posting as it might be helpful to others.
'Incidents (2)'[completionDate].[Dag] referencing a colomn. It is in your computation returning a table (multiple date in the evaluation context) instade of a scalar needed in DATEDIFF calculation.
You need to leverage to be sure that 'Incidents (2)'[completionDate].[Dag] is rturning a scalar value. To do that you can leverage rowcontext and then also formula like Max.
When I use SUM for example the intellisense of the editor shows me the columns of my table but when I use IF or Switch I'm not shown any column.
In this example of If (https://powerbi.microsoft.com/es-es/documentation/powerbi-desktop-tutorial-create-calculated-columns/) the column between [] works fine but when I put my column between [] I have error
error if
Any idea please?
Regards
I can see you are creating a measure while in the tutorial they are creating a calculated column. Measures and Calculated columns behave different, while creating a calculated column the expression you are using takes the context of each row so you can reference any column directly by [Column].
However measures evaluate in different context so they need an aggregation function to determine the value of your columns.
EXAMPLE: Calculated Column.
Is Red Calculated Column = IF([Color]="Red","Yes","No")
EXAMPLE: Measures.
Is Red Measure = IF(FIRSTNONBLANK([Color],0)="Red","Yes","No")
Note I used FIRSTNONBLANK aggregation function to access the [Color] column from a measure.
The above expression could not work for you depending on your measure, I only posted it for example purposes.
I found the answer
TotalHoras = SUMX(Horas;if(Horas[Tipo]="M";Horas[Duration]/60;Horas[Duration]))
Like #alejandrozuleta says Measures need an aggregation function to works