Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
Hi,
I have to grouped accumulations ;
A ; which does not work ;
= Table.Group(Source, {"Name", "Item"},
{{"Count", each
List.Generate( ()=> [ x = 0 , y = [Unit] {0} ] ,
each [x] < List.Count( [Unit] ) ,
each [ x = 0 , y = [y] + [Unit] {x} ] ,
each [y] )
} } )
and B; which does;
Table.Group(Source, {"Name", "Item"}, {{"Count", (i)=>
List.Generate( ()=> [ x = 0 , y = i[Unit] {0} ],
each [x] < List.Count( i [Unit] ) ,
each [ x = [x] + 1, y = [y] + i [Unit] {x} ] ,
each [y] )
}} )
As can be seen if defined the function (i)=> in the second, so is the first refering to an 'outside' table, while the 'each' in
generate is specifically whats going on within the List.Generate , so where both are each it gets confused and causes an error
or something like that ?
Rchard.
Solved! Go to Solution.
The each keyword is a syntax sugar, which is a shorthand form of "(_) =>". In the first case, only the each keyword is used. The program will find whether there is a Unit column in the variable (identifier) named "_" in the nearest layer.
The key point is:
The each keyword is a syntax sugar, which is a shorthand form of "(_) =>". In the first case, only the each keyword is used. The program will find whether there is a Unit column in the variable (identifier) named "_" in the nearest layer.
The key point is:
You have it correct.
Thanks, it took a while for the penny to drop when I kept getting an
error, at first I used a let statement, and named the [Units] and then I could use the name.
in generate.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.