I have a 3-column SharePoint list example in which these columns have a parent-child relationship. L1 would be a parent to L2, and L2 the parent of L3. The example list is in an image below.
I am reading these into a collection. To make it easy, each list item column value is one record, and the parent-child relationship is stored as properties in the collection (as opposed to making a JSON object with embedded objects showing the hierarchy.
Thus when the example list is read into a collection, the collection should look like this:
{Level: 1, LevelText: "Assemble group", Order: 1, P1: 0, P2: 0},
{Level: 1, LevelText: "Business item: Finance", Order: 2, P1: 0, P2: 0},
{Level: 2, LevelText: "Revenue Projections", Order: 1, P1: 2, P2: 0},
{Level: 2, LevelText: "Expense Levels", Order: 2, P1: 2, P2: 0},
{Level: 3, LevelText: "Personnel", Order: 1, P1: 2, P2: 2},
{Level: 3, LevelText: "Equipment", Order: 2, P1: 2, P2: 2},
{Level: 1, LevelText: "Business item: Letters", Order: 3, P1: 0, P2: 0},
{Level: 2, LevelText: "Contractors", Order: 1, P1: 3, P2: 0},
{Level: 3, LevelText: "Late Projects", Order: 1, P1: 3, P2: 1}
Those properties are required to be able to reconstruct the SP list. There are 9 values in the 5 rows of that list, and there should be 9 records in the collection.
The Level 1 "Assemble Group" is the first of the level 1 items (Order: 1). The two more Level 1 items "Business item: Finance" is the 2nd (Order: 2) and "Business items: Letters" (Order: 3)
The 2nd level 1 item has a Level 2 (Revenue Projections, Order: 1) and so its parent level 1 is the 2nd Level 1 item (Thus, P1: 2). Keeping track of the order of Level 2 under their Level 1, and Level 3 under Level 2 and Level 1, the values of P1 and P2 can be set logically.
In reading the SharePoint list, a top-to-bottom, left-to-right approach should do it.
The formula "strategy" I have is basically to set up a ForAll() which will iterate by item (row). Within that item (row), each column is evaluated to see if it has a string using Len() function. If L1 column has text, it creates the record for the level 1. If L2 has text, either within the item (row) or in the rows below with no other L1 column having text, its record is created, its parent L1 is added, and its order relative to other L2 items under that L1 parent is preserved, as well as designating its L1 parent with P1 value.
But the problem is in setting up a variable to keep track of the Order of at each level, so that the next record to be created has to reference that value to set properties. Moreover, a counter has to be created to increment the Order value when one is used. Additionally If() functions are probably not good here because something is wanted only if there is a true condition, and nothing is wanted (ie, do nothing) if there is a false condition.
Perhaps there is a strategy that is simpler. Or if the strategy is OK, then the formula is simple.
What do you think?
ForAll( SharePointListName,
If( Len(ThisRecord.L1) > 0,
Collect( ListData,
{
Level: 1,
LevelText: ThisRecord.L1,
Order: counter-of-level-1-items,
P1: 0, /* P1 and P2 always zero for Level 1 items */
P2: 0
});
UpdateContext({CurrentP1Order: counter-of-level-1-items }),
/* the false condition of If(), which is do nothing */
);
If( Len(ThisRecord.L2) > 0,
Collect( ListData,
{
Level: 2,
LevelText: ThisRecord.L2,
Order: counter-of-level-2-items-within-parent-level-1,
P1: order-value-of-parent-level-1,
P2: 0 /* P2 always zero for Level 2 items */
});
UpdateContext({CurrentP2Order: counter-of-level-2-items-within-parent-level-1 }),
/* the false condition of If(), which is do nothing */
);
If( Len(ThisRecord.L3) > 0,
Collect( ListData,
{
Level: 3,
LevelText: ThisRecord.L3,
Order: counter-of-level-3-items-within-parent-level-2,
P1: order-value-of-parent-level-1,
P2: order-value-of-parent-level-2
}),
/* the false condition of If(), which is do nothing */
)
)
Solved! Go to Solution.
I may be way off on your logic for your levels, but I believe you will get the concept in the following formula and can adjust as necessary:
ForAll( SharePointListName,
If(!IsBlank(ThisRecord.L1),
Collect( ListData,
{
Level: 1,
LevelText: ThisRecord.L1,
Order: CountRows(Filter(ListData, Level=1)),
P1: 0, /* P1 and P2 always zero for Level 1 items */
P2: 0
}
)
);
If(!IsBlank(ThisRecord.L2),
Collect( ListData,
{
Level: 2,
LevelText: ThisRecord.L2,
Order: CountRows(Filter(ListData, Level=2 && P1=1)),
P1: CountRows(Filter(ListData, Level=1)),
P2: 0 /* P2 always zero for Level 2 items */
}
)
);
If(!IsBlank(ThisRecord.L3),
Collect( ListData,
{
Level: 3,
LevelText: ThisRecord.L3,
Order: CountRows(Filter(ListData, Level=3 && P1=2)),
P1: CountRows(Filter(ListData, Level=1)),
P2: CountRows(Filter(ListData, Level=2))
}
)
)
)
I hope this is helpful for you.
I may be way off on your logic for your levels, but I believe you will get the concept in the following formula and can adjust as necessary:
ForAll( SharePointListName,
If(!IsBlank(ThisRecord.L1),
Collect( ListData,
{
Level: 1,
LevelText: ThisRecord.L1,
Order: CountRows(Filter(ListData, Level=1)),
P1: 0, /* P1 and P2 always zero for Level 1 items */
P2: 0
}
)
);
If(!IsBlank(ThisRecord.L2),
Collect( ListData,
{
Level: 2,
LevelText: ThisRecord.L2,
Order: CountRows(Filter(ListData, Level=2 && P1=1)),
P1: CountRows(Filter(ListData, Level=1)),
P2: 0 /* P2 always zero for Level 2 items */
}
)
);
If(!IsBlank(ThisRecord.L3),
Collect( ListData,
{
Level: 3,
LevelText: ThisRecord.L3,
Order: CountRows(Filter(ListData, Level=3 && P1=2)),
P1: CountRows(Filter(ListData, Level=1)),
P2: CountRows(Filter(ListData, Level=2))
}
)
)
)
I hope this is helpful for you.
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