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

How to patch a lookup column in a collection

Hello Everyone,

I hope all is well,

 

My issue:

I'm trying to patch a lookup result from a datavese table to a lookup column in a collection but it's not working out as expected.

 

What I have:

My tables:

 

Employees (Dataverser Table)

Employees Leave Balance (Collection)

No ( Primary)

Employee No (LookUp column on the No column in the table Employees)

 

My Expression:

Patch('Employee Leave Balances Col',Defaults('Employee Leave Balances Col'),
{
     'Employee Number': LookUp(Employees, No = EmpID).No

}
)

 

EmpID variable:

LookUp(‘Self Service Users', 'User Name' = username_txt_1.Text ).'Employee No.'.No

EmpID is successfully returning the expected text ("EMP-0149").

 

 

Thus, what is the solution to be able to patch a text value to the Employee Number column in the collection?

 

Any help would be highly appreciated,

 

Thank you 😁

1 ACCEPTED SOLUTION

Accepted Solutions

Try using the same column name in the collection that you are using in the table.  The code works for me when I do.  You'll notice the error says its expecting a record, but that the record has a different schema.  That tells me the issue is with the schema of the record in the collection.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

10 REPLIES 10
Pstork1
Most Valuable Professional
Most Valuable Professional

Is there a specific reason that you are using 'Employee Number' in the Patch when it appears the column is called 'Employee No'? The label in the record used for patching needs to match the column name.  But the following works for me:

Patch(
    'Employee Leave Balances Col',
    Defaults('Employee Leave Balances Col'),
    {
        Name: "TestRun",
        'Employee No': LookUp(
            Employees,
            No = EmpID
        )
    }
)

 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Hello @Pstork1 ,

 

That's the lookup column name in the "Employee leave balances", as you can see it's named "Employee Number":

Roberto_el_Hajj_0-1668935047661.png

 

I'm collecting all the values in the table mentioned above into a collection and patching a new row that contains the EmpID text in the column "Employee Number".

 

Additionally, I replaced "Employee No" with "Employee Number" because an error stated that "This column does not exist" .

So I tried the proposed expression but an error was thrown:

Roberto_el_Hajj_1-1668935658595.png

 

@Roberto_el_Hajj 

 

By replacing "Employee No" You mean rename it?  keep in mind if You rename a column in Sharepoint List, the Orginal Name that this column had on creation is still the reference. This means if You want to change the name of the column and make sure You can refer to it in Power App, You actually need to Delate the column and re-create it.

 

Most likely, you have the error about the column not existing cause it doesn't. SharePoint Still Calls the column Employee No or whatever it was Named when You first created it that means for patch column Employee number do not exist.


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.

Hello @SebS,

 

IM working with database and a collection, even tho i tried using the following expression:

Patch('Employee Leave Balances Col',Defaults('Employee Leave Balances Col'),
{
     'Employee Number': LookUp(Employees, No = EmpID).No

}
)

and I give the below error:

Roberto_el_Hajj_0-1668946022156.png

 

Sorry I did not read we are talking about Datavers my bad, and I'm not that experienced with them.

The error is the same as you will try to patch the outcome of a Selected.Value to a Choice field, that means You need to find the correct schema for what outcome of 'No' require to get to Your column Employee Number as right now they are not compatible and DB not accepting it.

 


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.

@Roberto_el_Hajj 

 

You must Miss something I think @Pstork1 is right, and he provided You with the right schema to patch this. also, look into this blog and Patch to Lookup column schema.

 

http://powerappsguide.com/blog/post/dataverse-how-to-patch-the-5-most-complex-data-types

 

hope it 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.

The other thing about your Patch that is different from mine is that you are putting the number itself into the collection.  In my case I'm adding it as a Lookup column, the difference is that I don't reference .No at the end of the Lookup.  The error you were getting early with my code is because I included the Name column from Dataverse in the Collection.  You evidently didn't.  But the Lookup column should be set using just the lookup and not the .No property of the lookup. Try this

Patch('Employee Leave Balances Col',Defaults('Employee Leave Balances Col'),
{
     'Employee Number': LookUp(Employees, No = EmpID)

}
)

 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Hello @Pstork1 ,I tested the expression above and the same error is still popping up:

Roberto_el_Hajj_0-1668969651307.png

 

Try using the same column name in the collection that you are using in the table.  The code works for me when I do.  You'll notice the error says its expecting a record, but that the record has a different schema.  That tells me the issue is with the schema of the record in the collection.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

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

Top Solution Authors
Top Kudoed Authors
Users online (4,255)