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

Patch Lookup column dataverse

Dear all, 

I'm struggling with a patch statement towards a lookup field in dataverse.  Let me try to explain my scenario.

I have following table defined in dataverse with the following relationships.

 

table : Inspection instruction

Dycons_1-1622468973366.png

Dycons_2-1622469019645.png

 

Further I made a gallery based on a collection. 

Dycons_3-1622469110902.png

I want to patch the entries of the collection towards the table inspection instruction in dataverse

 

To achieve this, i used follwing code :

 

 

Patch(
    Inspections,
    Defaults(Inspections),
    {
        Reference: gbl_InspRef,
        'Internal Reference': gbl_InspIntRef,
        Date: dte_DateInsp.SelectedDate,
        'Executed By': drp_ExecutedByInsp.SelectedText,
        Remark: txt_RemarkInsp.Text
    }
);

ForAll(
    col_InspInstr,
    Patch(
        [@'Inspection Instructions'],
        Defaults([@'Inspection Instructions']),
        {Reference: GUID(),
        'Inspection Reference': LookUp([@Inspections],Reference in gbl_InspRef
        'Instruction Reference': LookUp([@Instructions],Reference in col_InspInstr.Reference)}
    )
);

 

 

The statement  : "'Inspection Reference': LookUp([@Inspections],Reference in gbl_InspRef" gives me follwing error : 

Dycons_4-1622469299974.png

gbl_InspRef is a global variable defined in a previous screen and passed to this screen. (it's also used to patch into another table 'inspection')

 

The statement :  'Instruction Reference': LookUp([@Instructions],Reference in col_InspInstr.Reference) results in always the same record added, in this case C-VIK-026

Dycons_5-1622469592530.png

as i should expect C-VIK-026 and C-VIK-026-E as is in my collection

Dycons_0-1622469712872.png

 

What am i doing wrong.

 

You're help would be very appriciated

Kind regards

Steve 

 

 

7 REPLIES 7
CNT
Super User
Super User

@Dycons Firstly, LookUps and setting up a M-to-1 relationship does the same thing. Actually you are not using the relationship at all. You can choose which option you want. But I prefer Relationships as Dataverse does all the heavy lifting.

If you want to use the relationships, you patch all the other fileds and then you use the Relate command to set up the relationship,

Relate(Record in Inspection Instruction, Record in Inspection)

 

You can then use the dot(.) notation to refer to the related record,

Inspection1.InspectionInstruction

This will give all the Inspection Instructions for this Inspection.

 

Hope this helps!

@CNT , thanks for your reply but i'm afraid i didn't got it.

I tried following code

ForAll(
    col_InspInstr,
    Patch(
        [@'Inspection Instructions'],
        Defaults([@'Inspection Instructions']),
        {Reference: GUID(),
        'Instruction Reference': Relate(col_InspInstr,Inspections.'Inspection Instructions')}
    )
);

But then i receive following errors :

Dycons_0-1622474389924.png

 

@Dycons You can't have Relate and Patch nested. Patch is to Add/Modify records and Relate is to relate them into a relationship. Again, don't try to combine LookUp and Relate. You don't need both. Do the Patch first and then use the return value of the Patch to Relate.

ForAll(
    col_InspInstr,
    With({newInspectionInstructions=Patch(
        [@'Inspection Instructions'],
        Defaults([@'Inspection Instructions']),
        {Reference: GUID()}),
        Relate(col_InspInstr,newInspectionInstructions)
    )
);

Dear @CNT ,

 

I really appreciate your suggestion but unfortunately i'm still struggling with your code above. I really don't get it. (pretty sure this is my bad 😉)

 

I understand that the combination of lookup and relate is absolutely not needed, but what i miss in your above suggestion is how can add (save) the lookup value (field instruction reference of the 'Inspection instruction' table), which is the same as the field reference in the col_InspInstr. (but the lookup in Inspection instruction table is towards instruction table)

Dycons_0-1622993803303.png

So i don't understand why i have to use this code : 

        Relate(col_InspInstr,newInspectionInstructions)

As, col_InspInstr isn't the related table and newInspectionInstructions ony contains GUID() fields, not related to the inspection table, so i tried the following 

 

ForAll(
    col_InspInstr,
    With(
        {
            col_NewInspInstr: Patch(
                [@'Inspection Instructions'],
                Defaults([@'Inspection Instructions']),
                {Reference: GUID()}
            )
        },
        Relate(Instructions.'Inspection Instructions'.,col_NewInspInstr.'Instruction Reference');
    )
)

Which doesn't seems to work.

Sorry for my probably dumb questions 

 

Kind regards

 

Steve

 

 

@Dycons Ok, let leave Relate for another rainy day and just use LookUps. In your original code a bracket was missing. Maybe that could be the issue. So try this,

 

Patch(
    Inspections,
    Defaults(Inspections),
    {
        Reference: gbl_InspRef,
        'Internal Reference': gbl_InspIntRef,
        Date: dte_DateInsp.SelectedDate,
        'Executed By': drp_ExecutedByInsp.SelectedText,
        Remark: txt_RemarkInsp.Text
    }
);

ForAll(
    col_InspInstr,
    Patch(
        [@'Inspection Instructions'],
        Defaults([@'Inspection Instructions']),
        {Reference: GUID(),
        'Inspection Reference': LookUp([@Inspections],Reference in gbl_InspRef)
        'Instruction Reference': LookUp([@Instructions],Reference in col_InspInstr.Reference)}
    )
);

Dear @CNT , thanks again for your quick reply.  Hopefully it will be a rainy day so i can further investigate the relate function.  🙂

As i try the above code still the instruction reference is always the first one in the collection col_InspInstr.

Dycons_0-1623045884373.png

The result after patch and code above is always value C-VIK-019 

 

Dycons_1-1623045993553.png

So it seems as col_InspInstr.Reference in the forall loop is not taken the next value. (or the lookup towards instruction table is not working)

 

Kind regards

 

Steve

 

 

 

@Dycons 

Try replacing the LookUp like this,

LookUp([@Instructions],Reference in ThisRecord.Reference)

 

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 (913)