Canvas App embedded in Model Driven App Form - Patch with Lookup Column

(1) Share

Report

Posted on by ctedesco3307

892

Hi All - I have a canvas app that I am embedding in a model driven app form with a patch statement. one column in the table is a lookup column I can't seem to get the lookup column to populate on the form or update in the Patch statement. is this a limitation of embedded apps? It app controls work outside of the form

Approver Branch is my lookup column

Patch(
    'AP Location Approvers',
    LookUp(
        'AP Location Approvers',
        LocationApprovers = GUID(cmbnewprimary.Selected.LocationApprovers)
    ),
    {
       ApproverBranch:
       LookUp('AP Locations',xxxxx_apbranchlocationid=GUID(DataCardValue4.Selected.xxxxx_apbranchlocationid)),
       
        'Approver Level': 1,
        LOC: DataCardValue5.Text,
        IsPrimary:true
    }
);

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Haque 3,299 on at

Like (1)

Report
Copy link

Link copied!
Lookup columns require a specific object structure in Patch: To update a lookup column, we must patch it with an object containing the lookup's GUID and entity type, typically like this:

Patch( YourTable, Defaults(YourTable), { LookupColumn: { '@odata.type': "#Microsoft.Dynamics.CRM.<entitylogicalname>", Id: LookupRecordGUID } } )

In Dataverse (and Power Apps), to patch a lookup column, you must provide an object with the @odata.type and the GUID of the related record, like this:

Patch( 'AP Location Approvers', LookUp( 'AP Location Approvers', LocationApprovers = GUID(cmbnewprimary.Selected.LocationApprovers) ), { ApproverBranch: { '@odata.type': "#Microsoft.Dynamics.CRM.<entitylogicalname>", Id: GUID(DataCardValue4.Selected.xxxxx_apbranchlocationid) }, 'Approver Level': 1, LOC: DataCardValue5.Text, IsPrimary: true } );

Replace <entitylogicalname> with the logical name of the entity that ApproverBranch looks up to (e.g., "account", "contact", or your custom entity logical name).

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

11manish 2,487 on at

Like (0)

Report
Copy link

Link copied!
The first thing I'd test is:

ApproverBranch: DataCardValue4.Selected

because in Dataverse lookup patches, passing the selected record directly is usually the correct approach.

If that still fails, inspect JSON(DataCardValue4.Selected) to confirm the control is returning a Dataverse record from AP Locations rather than a custom record

or collection.

That will quickly reveal whether the issue is a lookup schema mismatch rather than a limitation of embedded Canvas Apps.

Was this reply helpful? Yes No