cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
RB2GSO
Advocate I
Advocate I

Joining two SharePoint lists into a collection

Hi everyone,

 

This is my first post, though I've used many of these posts to find my way through PowerApps development.  I'm a public school principal using PowerApps to make school administration more efficient and to harness a giant ecosystem of data so that teachers can make more informed instructional decisions.

 

One key piece of that is joining SharePoint lists into a collection, but I have been totally unsuccessful, despite reading a number of posts in this forum and doing a lot of Google searching & YouTube watching.  I'm hoping you all can help me get over this hurdle or point me to a solution that I have overlooked.

 

In this specific case, I am trying to join the following two SharePoint lists with the following (relevant) fields:

 

StudentsPSCurrent

  • StudentNumber   (number field)  (this is the relevant unique identifier)
  • FName  (single line of text field)
  • LName  (single line of text field)
  • HomeRoom  (single line of text field)

StudentAdmin

  • StudentNumber  (number field)  (this is the relevant unique identifier)
  • TranspPM  (single line of text field)

 

I'd like to create the collection colStudPSAdmin with these fields:

  • StudentNumber   (from StudentsPSCurrent)
  • FName  (from StudentsPSCurrent)
  • LName  (from StudentsPSCurrent)
  • HomeRoom  (from StudentsPSCurrent)
  • TranspPM  (from StudentAdmin)

 

I can create the collection, add the fields from the StudentsPSCurrent list, and add a text or number value into a TranspPM field of the collection.  That code is below:

 

RB2GSO_0-1631389688156.png

 

That successfully produces the collection, below:

 

RB2GSO_1-1631389831135.png

 

But, as soon as I add a lookup to use the TranspPM field from the StudentAdmin list as the text for the TranspPM field in the collection, I get an error saying that a text and a table can't be compared in the lookup.  Here's that code and the error:

 

RB2GSO_2-1631390289561.png

 

This same lookup code works everywhere else except in collections.  I've also tried

  • wrapping one or both lookup values in Value(... or Value(Text(...,
  • adding .Text or .Value to the end of one or both lookup values,
  • using ThisRecord instead of StudentsPSCurrent in the lookup (this does not throw an error in the editor, but it does not produce any rows in the collection), and
  • a lot of other things that were more or less (or not) intelligent.

 

I'm stuck!  I hope someone can help me get unstuck!

 

Thanks!

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Okay - a little slow to get back to this because it didn't work out of the gate and I haven't had the seat time to get it all sorted out.  Your suggestion was spot on with the same-named columns and helped me understand how the With function works.  With that, I was able to get done what I needed without the Add Columns portion.   The code snippet that worked is at the end of this post.

 

For those using this post in the future, the problem here was that the unique identifier column in each of the two tables I was trying to join had the same name. To get around it, we used the With and RenameColumns functions to give that column a different name in one of the tables. 

 

The RenameColumns function is pretty straightforward.  The With function less so.  The With function gives you a way to refer to a chunk of a formula with what is essentially a variable name.  This makes the primary formula more readable because the chunk of the formula you "With"ed is referred to simply with the variable name rather than all the details in that chunk of code. 

 

So, in this case, perhaps I didn't technically need to pull the RenameColumns chunk out using the With function, but that definitely makes the solution easier to read and understand.  Thanks, @WarrenBelz !

 

 

 

With(
    {
        NewStudAdmin: RenameColumns(
            StudentAdmin,
            "StudentNumber",
            "StudentAdminStuNum"
        )
    },
    ClearCollect(
        collectJoinStudPSAdmin,
        ForAll(
            StudentsPSCurrent,
            {
                StudNum: StudentNumber,
                StudFL: StudFLName,
                TranspPM: LookUp(
                    NewStudAdmin,
                    StudentAdminStuNum = StudentNumber,
                    TranspPM
                )
            }
        )
    )
)

 

 

 

View solution in original post

4 REPLIES 4
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @RB2GSO ,

Try this format

With(
   {
      wAdmin:
      RenameColumns(
         StudentAdmin,
         "StudentNumber",
         "StudentNo"
      )
   },
   ClearCollect(
      colStudPSAdmin,
      AddColumns(
         StudentsPSCurrent,
         "TransPM",
         LookUp(
            wAdmin,
            StudentNo = StudentNumber
         ).TransPM
      )
   )
)

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Thanks for the quick response, @WarrenBelz .

 

I gave that a shot and am getting errors in the With statement (see below):

RB2GSO_0-1631464892792.png

The error on With is "Name isn't valid.  This identifier isn't recognized."  The error on { is "Unexpected characters.  Characters are used in the formula in an unexpected way."

 

I've not used With before, so I tried adding parens to it, but that didn't work any better (see below):

RB2GSO_3-1631465432460.png

The error in the ClearCollect portion of the statement is "Behavior function in a non-behavior property.  You can't use this property to change values elsewhere in the app."

 

Is your line of attack renaming the StudentNumber field in the StudentAdmin list?

 

Thanks for the help!

Robin

 

 

WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @RB2GSO ,

Yes as far as the renaming (but also Delegation) - you should never name linking fields the same as it can lead to ambiguity on any lookup reference. I also forgot to add the field reference (now corrected), but that should not have caused the error you have. Below is some code I ran on a couple of test lists where the Title column is the linking field

WarrenBelz_0-1631479871869.png

It runs perfectly and produces the expected collection with the added field. Can you spot any difference to your references apart from the corrected code as mentioned.

I also have a blog on the With() statement that may be of use to you.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

 

Okay - a little slow to get back to this because it didn't work out of the gate and I haven't had the seat time to get it all sorted out.  Your suggestion was spot on with the same-named columns and helped me understand how the With function works.  With that, I was able to get done what I needed without the Add Columns portion.   The code snippet that worked is at the end of this post.

 

For those using this post in the future, the problem here was that the unique identifier column in each of the two tables I was trying to join had the same name. To get around it, we used the With and RenameColumns functions to give that column a different name in one of the tables. 

 

The RenameColumns function is pretty straightforward.  The With function less so.  The With function gives you a way to refer to a chunk of a formula with what is essentially a variable name.  This makes the primary formula more readable because the chunk of the formula you "With"ed is referred to simply with the variable name rather than all the details in that chunk of code. 

 

So, in this case, perhaps I didn't technically need to pull the RenameColumns chunk out using the With function, but that definitely makes the solution easier to read and understand.  Thanks, @WarrenBelz !

 

 

 

With(
    {
        NewStudAdmin: RenameColumns(
            StudentAdmin,
            "StudentNumber",
            "StudentAdminStuNum"
        )
    },
    ClearCollect(
        collectJoinStudPSAdmin,
        ForAll(
            StudentsPSCurrent,
            {
                StudNum: StudentNumber,
                StudFL: StudFLName,
                TranspPM: LookUp(
                    NewStudAdmin,
                    StudentAdminStuNum = StudentNumber,
                    TranspPM
                )
            }
        )
    )
)

 

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (630)