Hello,
This thread is resolve and junction documentation is missing on the web, community, youtube etc... so Enjoy reading for many to many custom relationship
I have 3 table, Idea --> 1:N --> Junction table <-- N:1 <-- Product
I have the following function :
ForAll(
cbIdea.SelectedItems,
Collect(
colideatopatchproduct,
{
Id: ThisRecord.ID,
Value: ThisRecord.Subject
}
)
);
ForAll(
cbproduct.SelectedItems,
Collect(
colProducttopatch,
{
Id: ThisRecord.ProductID,
Value: ThisRecord.Name
}
)
);
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: colProducttopatch.Value
}
)
I'm getting an error that it is expecting a record and found a table, I tried adding .value or .Id still doesn't make a change...
Solved! Go to Solution.
Okay that issue would be because of the comparison of guid and Text we can just try this instead to avoid conversion.
ForAll(
cbIdea.SelectedItems,
Collect(
colideatopatchproduct,
{
Id: ThisRecord.ID,
Value: ThisRecord.Subject
}
)
);
ForAll(
cbproduct.SelectedItems As cbprodselected,
Collect(
colProducttopatch,
{
Id: cbprodselected.ProductID,
Value: cbprodselected.Name
}
);
ForAll(
cbIdea.SelectedItems As ColIdeaSelPatch,
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: cbprodselected
Idea_L:ColIdeaSelPatch
}
)
)
);
Signature:
If you appreciated my comments/responses please be sure to Like/Kudo them it really does make me smile 🙂 !
Link to the Power Platform Professionals United Kingdom User Group:
I have had issues in the past where ThisRecord appears null/blank for a range of reasons and i have had issues when doing ForAlls within ForAlls (nested) because i cannot properly reference the one outside of the innermost ForAll and both make the resulting Record into ThisRecord. I found that by using As and calling thisrecord something it meant i knew what each record did as it wasnt a vague thisrecord and i could use it in nested scenarios such as our one.
I feel this link might be able to explain the As a bit incase I have not done the best job explaining:
https://powerapps.microsoft.com/en-us/blog/formulas-thisrecord-as-and-sequence/
The LookUp is essentially going to search for the Ideas that match the ones you have selected that have been saved in the collection by matching the IDs and pulls the record. As i did the ForAll through the collection I needed to use the LookUp but if you try my final solution it might be better as it should patch the record without the need to LookUp.
Also I had a question earlier but i think it got a bit buried. I was wondering why you are collecting the selectedItems do you use the collections for something?
Signature:
If you appreciated my comments/responses please be sure to Like/Kudo them it really does make me smile 🙂 !
Link to the Power Platform Professionals United Kingdom User Group:
Hey @Anonymous
which part has the error:
This last part jumps out to me so i am assuming it is here:
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: colProducttopatch.Value
}
)
How many records are you getting in colProducttopatch is it more than one if so i am expecting that part to look more like:
ForAll(colProducttopatch As prodbeingpatched,
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: prodbeingpatched.Value
}
)
)
if your only expecting the one i was expecting to see something more like:
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: First(colProducttopatch).Value
}
)
let me know how my suggestions go and if it doesn't work or i have misunderstood please do let me know 🙂
Signature:
If you appreciated my comments/responses please be sure to Like/Kudo them it really does make me smile 🙂 !
Link to the Power Platform Professionals United Kingdom User Group:
@AJ_Z ,
I have multiple record, I added your code but still the same error.
ForAll(
colProducttopatch As prodbeingpatched,
Patch(
Junction_Table_Idea_Products,
{JunctionID: Blank()},
{
Name: "test",
Product_L: prodbeingpatched.Value
}
)
)
Here is the structure
Table Product | 1:N | Junction Table | N:1 | Table Idea | |
A | Idea1 | ||||
B | Idea2 | ||||
C | Idea3 |
So when I enter my idea so let's say it is Idea number 3 and I select 3 product.
I want the junction table to be
Idea 3 - Product A
Idea 3 - Product B
Idea 3 - Product C
If I choose Idea 1 and select 2 product.
I want
Idea 1 A
Idea 1 B
with a table result :
A | Idea1 |
B | Idea1 |
A | Idea3 |
B | Idea3 |
C | Idea3 |
** Obviously the choose of product is selected combo box and the idea will be a "text" called Subject of the Idea.
Okay thanks for this explanation 🙂 what type of column is Product_L is it Choice?
Signature:
If you appreciated my comments/responses please be sure to Like/Kudo them it really does make me smile 🙂 !
Link to the Power Platform Professionals United Kingdom User Group:
That is the problem. In my solution I incorrectly assumed it was text so only part of my solution works. I am going to retype up the same solution with a change. Before I do so, am i right in saying that all products have a unique name?
Also, what is the items property for: cbproduct
Does the Value column in the collection colProducttopatch correspond to the name of the Product in the sharepoint field? If that column corresponds to a unique field there we can use that to patch a lookup. I can show you what I mean once you are able to confirm the questions I have 🙂 .
Signature:
If you appreciated my comments/responses please be sure to Like/Kudo them it really does make me smile 🙂 !
Link to the Power Platform Professionals United Kingdom User Group:
All Product should have a unique name yes. As of right now it is only text with an ID. ( But yes we are not suppose to have 2 product with the same name )
cbproduct :
I'm not using sharepoint but CDS ( Dataverse ) :
Okay this might not be the final solution as i am making some assumptions but I am just updating the solution options as I gather more information:
Option One
ForAll(
cbIdea.SelectedItems,
Collect(
colideatopatchproduct,
{
Id: ThisRecord.ID,
Value: ThisRecord.Subject
}
)
);
ForAll(
cbproduct.SelectedItems As cbprodselected,
Collect(
colProducttopatch,
{
Id: cbprodselected.ProductID,
Value: cbprodselected.Name
}
);
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: cbprodselected
}
)
);
Option 2
ForAll(
cbIdea.SelectedItems,
Collect(
colideatopatchproduct,
{
Id: ThisRecord.ID,
Value: ThisRecord.Subject
}
)
);
ForAll(
cbproduct.SelectedItems As cbprodselected,
Collect(
colProducttopatch,
{
Id: cbprodselected.ProductID,
Value: cbprodselected.Name
}
);
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: LookUp(Products,ProductID= cbprodselected.ProductID)
}
)
);
If neither of these work it is likely either due to the names of the columns or the fact that I made an assumption that ProductID is the GUID for a record in the Products table which has been selected.
Also I am assuming that the reason we ForAll through colProducttopatch is just to patch the selecteditems that we have collected for some other purpose but if it is to patch from other sources in the app aswell it would need to look more like:
Option 3
ForAll(
cbIdea.SelectedItems,
Collect(
colideatopatchproduct,
{
Id: ThisRecord.ID,
Value: ThisRecord.Subject
}
)
);
ForAll(
cbproduct.SelectedItems As cbprodselected,
Collect(
colProducttopatch,
{
Id: cbprodselected.ProductID,
Value: cbprodselected.Name
}
)
);
ForAll(
colProducttopatch As prodstopatch
Patch(
Junction_Table_Idea_Products,
Defaults(Junction_Table_Idea_Products),
{
Name: "Test",
Product_L: LookUp(Products,ProductID= prodstopatch.Id)
}
)
);
if none of these scenarios are your one I would like a screenshot of the column names from the products table and from the juction table. I have ordered the options in most likely to be your scenario
Signature:
If you appreciated my comments/responses please be sure to Like/Kudo them it really does make me smile 🙂 !
Link to the Power Platform Professionals United Kingdom User Group:
So far the option 1 seems to be right on. I'll run some test around it.
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