cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
wonderbeef
Frequent Visitor

Powerapps Having Difficulty with Sharepoint Lookup Field and Patching

Dealing with Sharepoint Lookup Columns has been frustrating me with this problem for the last few days. Essentially, when I try and patch a Collection's values to a Sharepoint List, everything seems to go great until I get to one Lookup field. I have tried three scenarios and they confusingly sway between Expected a Table and got a Record or Expected a Record and got a TableHere is the scenario

 

MySharepointList = Sharepoint List trying to be patched/inserted into

zRef_Plants = Source of Sharepoint lookup column in MySharepointList

data_ParsedJSONStream = Collection acting as datasource to patch to Sharepoint List

Problem Field = Sharepoint Column called Plant which is a lookup field for another table

 

The simplest code I could use to try and retrieve the Plant based on the default Combobox from Forms:

 

 

 

Patch('MySharepointList', {Title:"Test delete",
            Plant: LookUp(zRef_Plants, ID = field_somecombobox.Selected.Id)});

//Yields expected type 'Table' but got type 'Record' error

 

 

 

The large chunk of code... This looks complex because I am essentially making an Excel Uploader using JSON and PowerAutomate. It's important to note the below code works as intended UNLESS i put in the bit about the Plant lookup field. The typing prediction doesn't even recognize Plant as a potential field.

 

 

 

Patch(
    'MySharepointList',
    ForAll(
        data_ParsedJSONStream,
        Defaults('MySharepointList')
    ),
    ForAll(
        data_ParsedJSONStream,
        {
            Title: User().Email & "-" & "MRO " & Now() & ThisRecord.RequestType & ": " & ThisRecord.Description,
            'Request Type': LookUp(
                Choices([@'Requests - MRO Parts'].'Request Type'),
                Text(Value) = RequestType
            ),
            Description: Description,
            'Material #': MaterialNumber
            //The following lines all yield the same error if inserted of "Expecting a Record 
            //and got 'Table' value instead"
            //, Plant:field_Combobox.Selected
            //,Plant:LookUp(zRef_Plants, ID = field_PlantComboBox.Id)

        }
    )
);

 

 

 

So one statement says it needs a record and got a table, the other says it needs a table and got a record, yet it is the same code and same target... I tried clearing my cache and restarting the browser... Any help or workarounds would be much appreciated. Lookup columns feel very frustrating in PowerApps.

 

wonderbeef_0-1688946967098.pngwonderbeef_1-1688947034803.png

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @wonderbeef ,

I will firstly briefly comment that unless you are using that field directly in SharePoint Edit in Grid View, it is generally not necessary and will cause you unwanted complication - I never use them, but back to your issue.

Firstly, I do not know the Items of field_Combobox, so I have assumed the output is .Value - change if incorrect.

Another issue (not related to your problem) is that ForAll() is not designed to be a Loop, although it can work this way with considerable performance penalty as it does an individual Patch for each record. ForAll() creates a Table, which can be patched in one action provided its content is correct. For new records, this is simply a Table with field names and field types matching the list.

Also, Lookup fields need the ID (shown as Id) of the field item being looked up in the other list.
With all of that in mind, try this

ForAll(
   data_ParsedJSONStream As aData,
   Patch(
      'MySharepointList',
      {
         Title: User().Email & "-" & "MRO " & Now() & aData.RequestType & ": " & aData.Description,
         'Request Type': aData.RequestType,
         Description: aData.Description,
         'Material #': aData.MaterialNumber,
         Plant:
         {
            Value: field_Combobox.Selected.Value,
            Id: 
            LookUp(
               zRef_Plants,
               YourLookedUpField = field_Combobox.Selected.Value
            ).ID
         )
      }
   )
);

 

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.

MVP (Business Applications)   Visit my blog Practical Power Apps

View solution in original post

wonderbeef
Frequent Visitor

The problem was, in fact, that the Lookup field itself had Multiselect set to True. In this case, the Plant column expects a Table of records with a datatype for each. In that case, we use yet another ForAll statement to loop through the ComboBox's selected items and generate records. Here is the code that worked below:

 

Plant: ForAll(field_SomeComboBox.SelectedItems, {
                   '@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
                    Value:Value,
                    Id: Id
                })

 

 

A more generic solution to MultiSelect Sharepoint Lookup based Comboboxes for those in the future:

  Patch('YourSharepointList', {Title:"Test",
            LookupMultiSelectColumn:
                ForAll(YourComboBox.SelectedItems, {
       '@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
                    Value:Value,
                    Id: Id
                })
            }
        )

View solution in original post

5 REPLIES 5
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @wonderbeef ,

I will firstly briefly comment that unless you are using that field directly in SharePoint Edit in Grid View, it is generally not necessary and will cause you unwanted complication - I never use them, but back to your issue.

Firstly, I do not know the Items of field_Combobox, so I have assumed the output is .Value - change if incorrect.

Another issue (not related to your problem) is that ForAll() is not designed to be a Loop, although it can work this way with considerable performance penalty as it does an individual Patch for each record. ForAll() creates a Table, which can be patched in one action provided its content is correct. For new records, this is simply a Table with field names and field types matching the list.

Also, Lookup fields need the ID (shown as Id) of the field item being looked up in the other list.
With all of that in mind, try this

ForAll(
   data_ParsedJSONStream As aData,
   Patch(
      'MySharepointList',
      {
         Title: User().Email & "-" & "MRO " & Now() & aData.RequestType & ": " & aData.Description,
         'Request Type': aData.RequestType,
         Description: aData.Description,
         'Material #': aData.MaterialNumber,
         Plant:
         {
            Value: field_Combobox.Selected.Value,
            Id: 
            LookUp(
               zRef_Plants,
               YourLookedUpField = field_Combobox.Selected.Value
            ).ID
         )
      }
   )
);

 

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.

MVP (Business Applications)   Visit my blog Practical Power Apps

wonderbeef
Frequent Visitor

@WarrenBelz thank you for the quick reply.

 

  1. As you indicated, we are using the Edit Gridview administratively. At this point, if an internal Metadata choice is easier, I'd do it.
  2. The ForAll() within a Patch was selected because it was tested as faster somewhere on the forums and I have many rows within a Collection which I want to patch at once. In the screenshot below, the app takes an attachment and creates a grid of editable items stored in a collection and the value from the single combobox applied to all. When Submit is clicked, it writes that collection to Sharepoint. That is the point of tension

wonderbeef_0-1688993950436.png

3. Unfortunately, the format you provided yielded the error "Invalid argument type (Table). Expecting a Record value instead".

 

Any other suggestions? I looked at the Sharepoint field and it is a Lookup field with multi-select enabled, though I disabled it in the combobox At the end of the day, we're trying to keep these records linked to a "Plant" table. Is there a way to see what datatype it expects for the Plant argument?  Thank you again for the swift reply

wonderbeef
Frequent Visitor

The problem was, in fact, that the Lookup field itself had Multiselect set to True. In this case, the Plant column expects a Table of records with a datatype for each. In that case, we use yet another ForAll statement to loop through the ComboBox's selected items and generate records. Here is the code that worked below:

 

Plant: ForAll(field_SomeComboBox.SelectedItems, {
                   '@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
                    Value:Value,
                    Id: Id
                })

 

 

A more generic solution to MultiSelect Sharepoint Lookup based Comboboxes for those in the future:

  Patch('YourSharepointList', {Title:"Test",
            LookupMultiSelectColumn:
                ForAll(YourComboBox.SelectedItems, {
       '@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
                    Value:Value,
                    Id: Id
                })
            }
        )

@wonderbeef ,

Not something I could have known - I hope my structure guided you here.

@WarrenBelz you absolutely helped me get to the right train of thought and I appreciate you helping all of us out on the forum so quickly. 

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