cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

How to create records in Sharepoint Lists based tables having lookup fields, without enumerating all fields from looked-up table?

Hi,

 

EDIT - This solution summary will save the reading of the whole thread

Given these two Sharepoint Lists, where:

  • PatchedList.LkpColumn is a Lookup column to LookedUpList.LookedUpKey,
  • LookedUpKey has unique values:

Lists.JPG

In order to add a record to PatchedList, here is the syntax, specifically to handle the lookup field:

 

Patch(
    PatchedList,
    Defaults(PatchedList),
    {LkpColumn: 
        {
        Id: 1,
        Value: "Lorem"
        },
        Title:"A Title",
        AnyOtherMandatoryField: "A value"
    }
)

 

- Please note: "Id", not "ID" or "id".

- The "Value:" keyword refers to the LookedUp field in LookedUp list, whatever its actual name is.

 

Here is the result, assuming the original Title field has been renamed to PatchedListKey, and there are no other mandatory fields:

PatchedList.jpg

 

----------------------------------------------------------------------------------------------------------------

ORIGINAL POST

 

Summary:

Using Patch to create a record in a table from a Sharepoint list which has a Lookup column returns an error message.

 

Context:

- ParentTable: A parent (looked-up) table, with many fields. In this table, column 'Name' is the unique key. It is different from the Sharepoint provided auto-numbered ID column.

- ChildTable; a child table. It has a 'ParentName' lookup column, referring to ParentTable, Column 'Name'.

Both tables are Sharepoint Lists.

 

Goal:

Insert a record in ChildTable.

Avoid to enumerate all ParentTable fields: only 3 fields among many optional ones should be filled in when creating the record.

 

Attempt:

Patch(ChildTable,
Defaults(ChildTable),
{
ParentName: LookUp(ParentTable, Name = "AnyExistingName"),

OtherFields: OtherValues
}
)

 

Result:

Invalid argument type. Expecting a record value, but of a different schema.

Missing column. Your formula is missing a column 'Id' with type 'Number'

 

Same error when removing the OtherFields: OtherValues lines. Confirms the error comes from the first line.

 

Investigations:

 

1. True, [LookUp(ParentTable, Name = "AnyExistingName")] does not have all the fields of the Sharepoint ParentTable list, specifically not the ID field.

 

2. In Sharepoint, displaying the ParentTable ListSettings confirms that the ID field is not listed in the Columns list.

Many attempts to work it around, like Lookup(AddColumns(ParentTable, "ID", Blank()) or Lookup(AddColumns(ParentTable, "ID", 0) , etc. all return an error message.

 

Also found on the Web a lot of threads, which suggest to use a "ATSIGNodata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser" syntax.

For this syntax to work, all of these threads suggest to explicitly list all fields of ParentTable, like this:

{ParentName:

{OddDataTypeSyntax,

field1:value1,

- - etc. - - ,

fieldn:valuen}

}

This should preferably be avoided. One reason is that there are many fields in the Parent table. The second reason is that some more optional fields might be added in the future, and the code should still work with these extra fields, provided naturally that the data connector to ParentTable is refreshed in PowerApp.

 

The question:

So, long story short, how can we create a record in ChildTable, filling up the ParentName lookup column?

 

Thank you.

2 ACCEPTED SOLUTIONS

Accepted Solutions

@LapisLazuli 

 

 

The issue is intelisense it's changing id to ID and i never notice that till I build the app 🙂

 

Two Tables

 

TestApp = ParentTable

TestApp2 = ChildTable

 

ChildTable under Name have lookup table to ParentName column in TestApp

 

TestApp List

SebS_0-1685094353205.png

TestApp2 list

SebS_1-1685094402056.png

 

Now I created an app

 

SebS_2-1685094437931.png

 

Button Add Parent contain below Code what will relate Parent to Child table column Name base on ParentNames

 

Patch(
    TestApp2,
    Gallery1.Selected,
    {
        Name: {
            Id: Dropdown1.Selected.ID,
            Value: Dropdown1.Selected.ParentName
        }
    }
)

 

from Dropdown I picking "Gary"

 

SebS_3-1685094536699.png

I pointing in gallery to second record to select it and I'm pressing button

 

 

Result joe change to Gary

SebS_4-1685094598356.png

Now in the SharePoint List lookup Column Name second record change to Gary what is a parent in TestApp List

 

SebS_5-1685094647900.png

Hope this helps

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

View solution in original post

@SebS 

Congratulations! You found the reason: It should not be ID, or id, but Id !!!

Very helpful, thank you. I'll summarize the solution in the original post, to save the other readers the need to browse through all this discussion.

 

View solution in original post

13 REPLIES 13
SebS
Super User
Super User

@LapisLazuli 

 

How You providing "AnyExistingName" ? it's picked from dropdown or user typing it in InputText box ?

Also both lists are SharePoint list and only relation between them is the Name ? right but You want populate ListA Lookup Column with ListB Record right ?

 

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Hi,

Thank you for taking the time to review the question.

Re: "How You providing "AnyExistingName" ? it's picked from dropdown or user typing it in InputText box ?"

Eventually, another table will be looped through, and one of its field will provide the value.

But to perform the testing, I kept it very simple: "AnyExistingName" is hard-coded, picked from an existing value in ParentTable.Name column.

Re: "Also both lists are SharePoint list"
Yes, as mentioned.
Re: "only relation between them is the Name ?"

Yes

Re: "You want populate ListA Lookup Column with ListB Record right ?"

Correct. With the names that I provided, the aim is to populate 'ChildTable.ParentName' with the record of 'ParentTable' which column 'Name' is 'AnyExistingName'. Column 'Name' being a unique key of 'ParentTable'.

ParentChild.jpg

Hope this clarifies.

Regards

@LapisLazuli 

 

The ParentName is a lookup column, and in SharePoint, you can relate the column just by picking Name from ParentTable, which will be reflected in the Lookup column, and You can choose what data will be displayed.

 

Now when You use Patch, there is a specific Schema for how you can Patch to the Lookup column.

 

 

Patch(
      Datasource,
      Defaults(Datasource),

      {
       ParentName:
                {
                 ID:99
                 Value:"AnyExistingName"
                },
       OtherData:"other"
      }
)

 

 

So you need to source two parameters. Why do I ask how You pick AnyExistingName cause it's important how you provide it to patch but let's say it's magically showing up 🙂

 

 

With({Parent:LookUp(ParentTable, Name = "AnyExistingName")},

Patch(ChildTable,
Defaults(ChildTable),
{
ParentName: {
             ID:Parent.ID,
             Value:Parent.Name
            },

OtherFields: OtherValues
}
)

 

 

Just keep in mind this will be valid only when all names are unique and you will have no duplicate names


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Thank you for your time.

Well noted the With() function, which simplifies the syntax.

However, unfortunately, it didn't work. I still get the same message.

 

The reason is now however unclear. On one side, 

 

Parent:LookUp(ParentTable, Name = "AnyExistingName"

still has no ID, since ParentTable doesn't. See my post.

What I don't understand now, is why I get the same error message. I should get an error on:

             ID:Parent.ID,

saying that there is no such column in Parent. Am I missing something?

 

Side question:

             Value:Parent.Name

Do you rather mean :

Name:Parent.Name

 

Thanks. 

@LapisLazuli 

 

Let's clarify something if we are talking about two SharePoint Lists. There is no option that one of them does not have an ID column, or the column is blank. The ID column is system-generated and auto-incremented and exists in all Sharepoint lists.

 

I may mix ways how you want to relate the tables, but the concept will be the same.


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

@LapisLazuli 

 

Now to the lookup column

 

In SharePoint when you set up one You will have this prompt

 

SebS_0-1685046650141.png

 

How this work is first You picking List what become source of the lookup column than you picking Column what will be the main Source of Display Data the relationship is build by ID of the record and that's why when you patching ID is importend.

 

{

ID: <--- ID of Record in Sharepoint auto Generated ID Column

Value: <--- Data Showing / Existing in Column Chosen by You when You was creating LookupColumn

}

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

@SebS,

Thanks for the clarification ID/Value in Lookup columns.

Regarding the missing ID, it looks like my interpretation of the message is incorrect. However, I still get the same error message when trying your suggestion.

Let me investigate further, and come back with more details. Or hopefully a solution.

Thanks again for the time you spent on this question.

 

@LapisLazuli 

 

I'm more than happy to assist. Keep in mind if you want to show a gallery of parents and then when user clicks on a name of a parent you want to display all Children of that parent or the opposite you do not need the Lookup column

 

The lookup Column is Complex type and will create a lot of pain with Delegations and other things.

 

What You can do instead is create a fake relationship in SharePoint List and manage User Experience in Power App

 

What that means :

 

Parents have an ID now in Child Table you create a column caled ParentID and then You using Patch to add ID of a Parent to each new Child Record

 

What will look like this

 

ParentTable

 

ID: 1 ParentName: Chris

 

ChildTable

 

ID:1 Name:Joe ParentID:1

ID:2 Name:Santa ParentID:1

 

Result Parent Chris got two kids Joe and Santa 🙂

now in Power Apps, you create a gallery Parent and Gallery Child

 

Gallery parent Item property will be ParentTable, and Gallery Child item property will be Filter(ChildTable, ID = Galery_Parent.Selected.ID)

 

When the user will click on a parent all records with this parent ID will be displayed in ChildGallery.

 

hope this has sense keep in mind you can also nest galleries.

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

View LookedUpList 

View PatchedList 

Download .msapp file 

 

 

@SebS 

Hi,

Despite your help, I'm still stuck with the original question.

I can't manage to have this code work:

Patch(
      Datasource,
      Defaults(Datasource),

      {
       ParentName:
                {
                 ID:99
                 Value:"AnyExistingName"
                },
       OtherData:"other"
      }
)

In order to illustrate, I've created the two lists and a PowerApp app.

 

View LookedUpList 

View PatchedList 

Download .msapp file 

 

Here are the lists:

9ff408fc-3db1-49a7-acfd-68719c122051.jpg

The App connects to this two lists. It has a single screen, with a single button. The OnSelect code is shown below. 

 

Code.JPG

 

The error message is still the same.

Error.JPG

 

 

What's wrong?

 

Thanks and regards

 

View LookedUpList 

View PatchedList 

Download .msapp file 

 

 

 

 

 

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