Hi
I have 3 tables,
1) list of all my material numbers (uniqe list of material numbers)
2) list of all my recieved materials (same material number appears multiple times)
3) list of all my sold materials (same material number appears multiple times)
I would like to make a gallery based on the first table - and then add columns showing the sum of the recieved materials of the given material (table 2) and the sum of the sold materials of the given material (table 3)... Until a selected date...
Some how the formular below show the same value for each material - how do I get the correct invidual values?
AddColumns(Table_Materials;
"Recieved";
Sum(Filter(Table_Recieved;Materialnumber=Value(Materialnumber);Period<=DatePicker1.SelectedDate);QTY);
"Sold";
Sum(Filter(Table_Sold;Materialnumber=Value(Materialnumber);Period<=DatePicker1.SelectedDate);QTY)
)
Solved! Go to Solution.
Hi @jlke-as ,
I do not know what your actual tables look like, but the below example should give you some direction:
Suppose this Collection is Table 1 (unique list of materials):
ClearCollect(
myMaterials,
{MaterialNumber: 1},
{MaterialNumber: 2},
{MaterialNumber: 3},
{MaterialNumber: 4},
{MaterialNumber: 5},
{MaterialNumber: 6},
{MaterialNumber: 7},
{MaterialNumber: 8},
{MaterialNumber: 9},
{MaterialNumber: 10}
);
Table 2 (Received Materials):
ClearCollect(
myMaterialsRecieved,
{MaterialRecievedNo: 1, DateRecieved: Date(2023,1,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,1,1)},
{MaterialRecievedNo: 1, DateRecieved: Date(2023,2,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,2,1)},
{MaterialRecievedNo: 3, DateRecieved: Date(2023,3,1)},
{MaterialRecievedNo: 1, DateRecieved: Date(2023,3,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,4,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,4,1)},
{MaterialRecievedNo: 3, DateRecieved: Date(2023,5,1)},
{MaterialRecievedNo: 5, DateRecieved: Date(2023,5,1)}
);
Table 3 (Sold Materials)
ClearCollect(
myMaterialsSold,
{MaterialSoldNo: 3, DateSold: Date(2023,5,1)},
{MaterialSoldNo: 5, DateSold: Date(2023,5,1)},
{MaterialSoldNo: 2, DateSold: Date(2023,6,1)},
{MaterialSoldNo: 1, DateSold: Date(2023,6,1)},
{MaterialSoldNo: 5, DateSold: Date(2023,7,1)},
{MaterialSoldNo: 6, DateSold: Date(2023,7,1)},
{MaterialSoldNo: 7, DateSold: Date(2023,8,1)},
{MaterialSoldNo: 5, DateSold: Date(2023,8,1)},
{MaterialSoldNo: 2, DateSold: Date(2023,9,1)},
{MaterialSoldNo: 7, DateSold: Date(2023,9,1)}
);
Apply the below to the Items property in your Gallery. Note the reference to a Date Picker field:
With(
{
_recieved_items: AddColumns(
GroupBy(//duplicate the item number as a new column
AddColumns(
Filter(
myMaterialsRecieved,
DateRecieved <= DatePickerUntil.SelectedDate
),
"MaterialRecievedNumber",
MaterialRecievedNo
),
"MaterialRecievedNo",
"_Grouped_recieved"
),
"Recieved",
CountRows(ThisRecord._Grouped_recieved)
)
},
With(
{
_sold_items: AddColumns(
GroupBy(//duplicate the item number as a new column
AddColumns(
Filter(
myMaterialsSold,
DateSold <= DatePickerUntil.SelectedDate
),
"MaterialSoldNumber",
MaterialSoldNo
),
"MaterialSoldNumber",
"_GroupedSold"
),
"Sold",
CountRows(ThisRecord._GroupedSold)
)
},
AddColumns(
myMaterials,
"Count Recieved",
LookUp(
_recieved_items,
MaterialRecievedNo = MaterialNumber,
Recieved
),
"Count Sold",
LookUp(
_sold_items,
MaterialSoldNumber = MaterialNumber,
Sold
)
)
)
)
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
Hi @jlke-as ,
I do not know what your actual tables look like, but the below example should give you some direction:
Suppose this Collection is Table 1 (unique list of materials):
ClearCollect(
myMaterials,
{MaterialNumber: 1},
{MaterialNumber: 2},
{MaterialNumber: 3},
{MaterialNumber: 4},
{MaterialNumber: 5},
{MaterialNumber: 6},
{MaterialNumber: 7},
{MaterialNumber: 8},
{MaterialNumber: 9},
{MaterialNumber: 10}
);
Table 2 (Received Materials):
ClearCollect(
myMaterialsRecieved,
{MaterialRecievedNo: 1, DateRecieved: Date(2023,1,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,1,1)},
{MaterialRecievedNo: 1, DateRecieved: Date(2023,2,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,2,1)},
{MaterialRecievedNo: 3, DateRecieved: Date(2023,3,1)},
{MaterialRecievedNo: 1, DateRecieved: Date(2023,3,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,4,1)},
{MaterialRecievedNo: 2, DateRecieved: Date(2023,4,1)},
{MaterialRecievedNo: 3, DateRecieved: Date(2023,5,1)},
{MaterialRecievedNo: 5, DateRecieved: Date(2023,5,1)}
);
Table 3 (Sold Materials)
ClearCollect(
myMaterialsSold,
{MaterialSoldNo: 3, DateSold: Date(2023,5,1)},
{MaterialSoldNo: 5, DateSold: Date(2023,5,1)},
{MaterialSoldNo: 2, DateSold: Date(2023,6,1)},
{MaterialSoldNo: 1, DateSold: Date(2023,6,1)},
{MaterialSoldNo: 5, DateSold: Date(2023,7,1)},
{MaterialSoldNo: 6, DateSold: Date(2023,7,1)},
{MaterialSoldNo: 7, DateSold: Date(2023,8,1)},
{MaterialSoldNo: 5, DateSold: Date(2023,8,1)},
{MaterialSoldNo: 2, DateSold: Date(2023,9,1)},
{MaterialSoldNo: 7, DateSold: Date(2023,9,1)}
);
Apply the below to the Items property in your Gallery. Note the reference to a Date Picker field:
With(
{
_recieved_items: AddColumns(
GroupBy(//duplicate the item number as a new column
AddColumns(
Filter(
myMaterialsRecieved,
DateRecieved <= DatePickerUntil.SelectedDate
),
"MaterialRecievedNumber",
MaterialRecievedNo
),
"MaterialRecievedNo",
"_Grouped_recieved"
),
"Recieved",
CountRows(ThisRecord._Grouped_recieved)
)
},
With(
{
_sold_items: AddColumns(
GroupBy(//duplicate the item number as a new column
AddColumns(
Filter(
myMaterialsSold,
DateSold <= DatePickerUntil.SelectedDate
),
"MaterialSoldNumber",
MaterialSoldNo
),
"MaterialSoldNumber",
"_GroupedSold"
),
"Sold",
CountRows(ThisRecord._GroupedSold)
)
},
AddColumns(
myMaterials,
"Count Recieved",
LookUp(
_recieved_items,
MaterialRecievedNo = MaterialNumber,
Recieved
),
"Count Sold",
LookUp(
_sold_items,
MaterialSoldNumber = MaterialNumber,
Sold
)
)
)
)
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
Hi Amik
Thanks for your reply...
I still have the same number in all rows in my gallery....
Could I be due to the fact that the coloumn material number is called "Material number" in all 3 tables?
(in your example the columns have been named three different names...)
Could it be solved by using "@" in some of the cases?
Hi again
Further more I don't need to count the rows... I need to sum them...
(a column of QTY is needed to be added to the recieve- and sold data sources)
I am wondering, why the "addcolumns"-formular needs to be this complex...
The two yellow columns should show the same figures
- the left one is a part of the "ITEMS" based on your code
- the rigth one is a text label in my gallery showing the figures that I need... You can see my code in the image (but as it is not a part of the gallery, then I cannot filter the gallery based on the figures... And I need to do so... 😉 )
Hi @jlke-as ,
If the column heading is the same across all 3 tables, you can use the Rename Columns function to explicitly reference the correct record.
With(//group each material number x number of times they appear in the table
{
_recieveditems: DropColumns(
AddColumns(
GroupBy(
RenameColumns(
Filter(
myMaterialsRecieved,
DateRecieved < DatePickerUntil.SelectedDate
),
"MaterialNumber",
"_recieved_material_no"
),
"_recieved_material_no",
"GroupedItems"
),
"Count Recieved",
CountRows(GroupedItems)
),
"GroupedItems"
)
},
With(//group each material number x number of times they appear in the table
{
_solditems: DropColumns(
AddColumns(
GroupBy(
RenameColumns(
Filter(
myMaterialsSold,
DateSold < DatePickerUntil.SelectedDate
),
"MaterialNumber",
"_sold_material_num"
),
"_sold_material_num",
"GroupedItems"
),
"Count Sold",
CountRows(GroupedItems)
),
"GroupedItems"
)
},
AddColumns(
myMaterials,
"Count Recieved",
LookUp(
_recieveditems,
_recieved_material_no = MaterialNumber,
'Count Recieved'
),
"Count Sold",
LookUp(
_solditems,
_sold_material_num = MaterialNumber,
'Count Sold'
)
)
)
)
We do not SUM because there is nothing to SUM. Instead, you want to COUNT the number of occurrences each Material Number appears in the other two tables.
Regarding the complexity – there is always going to be someone smarter who could produce a more elegant solution, but this is my attempt, and it works.
If you need to understand what this expression is doing, I would suggest breaking up the expression into smaller parts to identify what each section is trying to do, and then see how it all links up together.
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
Hi @jlke-as,
Based on the provided information, you have three tables with the following structure:
Table_Materials:
ClearCollect(
Table_Materials,
{MaterialNumber: 1},
{MaterialNumber: 2},
{MaterialNumber: 3},
{MaterialNumber: 4},
{MaterialNumber: 5},
{MaterialNumber: 6},
{MaterialNumber: 7},
{MaterialNumber: 8},
{MaterialNumber: 9},
{MaterialNumber: 10}
);
Table_Received:
ClearCollect(
Table_Recieved,
{
Materialnumber: 1,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
1,
1
)
},
{
Materialnumber: 2,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
1,
1
)
},
{
Materialnumber: 1,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
2,
1
)
},
{
Materialnumber: 2,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
2,
1
)
},
{
Materialnumber: 3,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
3,
1
)
},
{
Materialnumber: 1,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
3,
1
)
},
{
Materialnumber: 2,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
4,
1
)
},
{
Materialnumber: 2,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
4,
1
)
},
{
Materialnumber: 3,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
5,
1
)
},
{
Materialnumber: 5,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
5,
1
)
}
);
Table_Sold:
ClearCollect(
Table_Sold,
{
MaterialNumber: 3,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
5,
1
)
},
{
MaterialNumber: 5,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
5,
1
)
},
{
MaterialNumber: 2,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
6,
1
)
},
{
MaterialNumber: 1,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
6,
1
)
},
{
MaterialNumber: 5,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
7,
1
)
},
{
MaterialNumber: 6,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
7,
1
)
},
{
MaterialNumber: 7,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
8,
1
)
},
{
MaterialNumber: 5,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
8,
1
)
},
{
MaterialNumber: 2,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
9,
1
)
},
{
MaterialNumber: 7,
QTY: RandBetween(
5,
10
),
Period: Date(
2023,
9,
1
)
}
);
To obtain the sum of received and sold items based on the selected item in the gallery and applying a date filter, you can follow these steps:
ClearCollect(
newTable,
AddColumns(
Table_Materials,
"Recieved",
0,
"Sold",
0
)
);
Patch(
newTable,
ThisItem,
{
Recieved: Sum(
Filter(
Table_Recieved,
Materialnumber = Value(ThisItem.MaterialNumber),
Period <= DatePicker1.SelectedDate
),
QTY
),
Sold: Sum(
Filter(
Table_Sold,
MaterialNumber = Value(ThisItem.MaterialNumber),
Period <= DatePicker1.SelectedDate
),
QTY
)
}
)
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages