Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreShape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.
Hello, need to create a calculated column to label each row item in my table as what batch. So batch 1 is the first 200 row items then batch 2 for the succeeding row items and so on .
Solved! Go to Solution.
define
column
// First, create manually this column in your table...
'Statistics'[Helper] = rand()
column 'Statistics'[Index] =
// Then this one...
var currentHelper = 'Statistics'[Helper]
var Index =
COUNTROWS(
filter(
'Statistics',
'Statistics'[Helper] <= currentHelper
)
)
return Index
column Statistics[BatchId] =
// Then this is going to be the one you need.
// Hide the other two. Adjust the Batch BatchCount
// variable.
var RowCount = COUNTROWS( Statistics )
var BatchCount = 5
var Length = int( RowCount / BatchCount )
var BatchId = QUOTIENT( Statistics[Index], Length )
return
BatchId
// TESTING...
EVALUATE
'Statistics'
order by
Statistics[BatchId]
The above is test code that works in DAX Studio with any table you want (mine was called Statistics). All you have to do is to create the 3 columns (in the order of appearance) in your table. The sad thing is that if you want to do such things in DAX in the most general way, you have to use the random numbers...
Hello, much as i want to use power query for this, it is a calculated table created in dax hence i will need a dax calculated column. so basically i just need to create a index that will change for every 200 row items. thanks
OK... I understand you're not worried about which rows will get which batch number? What kind of columns do you have in the table? Is there one that is unique?
Yes you are right i just need to divide the entire table into batches. currently i have 856 rows, so will need to put them in 5 batches. Unfortunately i do not have columns that have unique values
define
column
// First, create manually this column in your table...
'Statistics'[Helper] = rand()
column 'Statistics'[Index] =
// Then this one...
var currentHelper = 'Statistics'[Helper]
var Index =
COUNTROWS(
filter(
'Statistics',
'Statistics'[Helper] <= currentHelper
)
)
return Index
column Statistics[BatchId] =
// Then this is going to be the one you need.
// Hide the other two. Adjust the Batch BatchCount
// variable.
var RowCount = COUNTROWS( Statistics )
var BatchCount = 5
var Length = int( RowCount / BatchCount )
var BatchId = QUOTIENT( Statistics[Index], Length )
return
BatchId
// TESTING...
EVALUATE
'Statistics'
order by
Statistics[BatchId]
The above is test code that works in DAX Studio with any table you want (mine was called Statistics). All you have to do is to create the 3 columns (in the order of appearance) in your table. The sad thing is that if you want to do such things in DAX in the most general way, you have to use the random numbers...
This is nice! just some few clarification:
1 the first column basically creates a unique value for each row right?
2. what if i already have a unique column but is it is not a number, how will i be able to cummulatively count the rows?
3. If i already have a define length, let's say 200 i can already proceed with
ar BatchId = QUOTIENT( Statistics[Index], Length )
to assign value of length to 200 right?
1. Yes. But it's possible with rand(), even though highly improbable, that you could get 2 same values. But that should not matter much...
2. If you have a unique column and its values are comparable (even strings are), then you can use it instead of the one with rand(). The logic is exactly the same.
3. Yes, instead of defining how many batches you want, you can directly specify how long a batch
should be. Then, you don't have to calculate the length of the batch and the formula above is correct.
Ok one last thing if ever i want to put this in a measure what will the changes to be made?
Don't ever put this in a measure because it relies on RANDOM NUMBERS. This means every time you run it, rows can be assigned a different batch id... and unless you're OK with that (are you?), you should not use it as a measure.
Please use Power Query for this, not DAX. But to give you the exact solution... we need data to work with. To be able to do it in DAX, your table would have to have a field to sort it on. This is definitely a job for PQ.
User | Count |
---|---|
25 | |
21 | |
20 | |
13 | |
13 |
User | Count |
---|---|
40 | |
28 | |
28 | |
22 | |
21 |