cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper II
Helper II

Dynamics 365 Patching to Lookup Column

Hi all,

 

I have a Dynamics 365 instance with a custom entity. I want to create a PowerApps form that patches to the entity. The entity contains a look field named "Team" that links to the "System Teams" entity. There's also another lookup field that links with "Account". Below is my code:

 

ClearCollect(
    Submission,
    {
        BSC_Name : Name.Text,
        BSC_Customer : SelectedAccount.Account,
        BSC_Background : Background.Text,
        BSC_Scope : Scope.Text,
        BSC_ExpectedCloseDate : Deadline.SelectedDate,
        BSC_RaisedBy : Value(Department.Selected.ID),
        BSC_SuggestedTeam : Team.Selected.'System Teams'
    }
);
Set(LocalSubmission, First(Submission));
Set(TeamRecord, LookUp('System Teams', 'System Teams' = LocalSubmission.BSC_SuggestedTeam));
Patch(
    'Records',
    Defaults('Records'),
    {
        Name : LocalSubmission.BSC_BluespaceName,
        testexc_bluespacename : LocalSubmission.BSC_Name, //Legacy Field
        Customer : GUID(LocalSubmission.BSC_Customer),
        'Opportunity Background (Include contact name)' : LocalSubmission.BSC_Background, //Legacy Field
        Background : LocalSubmission.BSC_Background,
        testexc_opportunitydescription : LocalSubmission.BSC_Scope, //Legacy Field
        Scope : LocalSubmission.BSC_Scope,
        testexc_estclosedate : LocalSubmission.BSC_ExpectedCloseDate,
        testexc_departmentraisedby : LocalSubmission.BSC_RaisedBy, //Legacy Field
		
        testexc_destinationteam : TeamRecord
		
    }
);
Navigate(Complete,ScreenTransition.None)

It appears that if I exclude "testexc_destinationteam : TeamRecord" everything works okay. If I configure in the same form as the "Account" entry it states a record is expected not a GUID. If I keep it like the above it states that a value must be provided for item.


Does anyone have any idea why this is happening?

 

Thanks,

J

 

 

 

4 REPLIES 4
Highlighted
Responsive Resident
Responsive Resident

Re: Dynamics 365 Patching to Lookup Column

Hi,

 

Are you sure its getting the record - Set(TeamRecord, LookUp('System Teams', 'System Teams' = LocalSubmission.BSC_SuggestedTeam));

 

Once check with some static value like First('System Teams').

 

If this answers your questions give Thumbs up and mark it as verified.

Regards,

Pavan Kumar Garlapati

Highlighted
Helper II
Helper II

Re: Dynamics 365 Patching to Lookup Column

Hi @PavanKumar 

 

Yes, it's pulling the correct record. I've checked the variables in the app and can see that this is being populated.

 

Thanks,

J

Highlighted
Responsive Resident
Responsive Resident

Re: Dynamics 365 Patching to Lookup Column

Hi,

 

As mentioned once double check the column name if you are correctly mapping to Lookup column also once try with First('System Teams') and see if its working.

 

If this answers your question mark it as verified and give thumbs up

Regards,

Pavan Kumar Garlapati

Highlighted
Helper II
Helper II

Re: Dynamics 365 Patching to Lookup Column

Hi @PavanKumar 

 

I've tried your suggestion:

ClearCollect(
    TeamRecordCollection,
    Filter(
        'System Teams',
        'System Teams' = LocalSubmission.BSC_SuggestedTeam
    )
);
Patch(
    'Bluespace records',
    Defaults('Bluespace records'),
    {
        Name : LocalSubmission.BSC_Name,
        testexc_bluespacename : LocalSubmission.BSC_Name, //Legacy Field
        Customer : GUID(LocalSubmission.BSC_Customer),
        'Opportunity Background (Include contact name)' : LocalSubmission.BSC_Background, //Legacy Field
        Background : LocalSubmission.BSC_Background,
        testexc_opportunitydescription : LocalSubmission.BSC_Scope, //Legacy Field
        Scope : LocalSubmission.BSC_Scope,
        testexc_estclosedate : LocalSubmission.BSC_ExpectedCloseDate,
        testexc_departmentraisedby : LocalSubmission.BSC_RaisedBy, //Legacy Field
        testexc_destinationteam : First(TeamRecordCollection)
    }
);

However I'm getting the same issue. I had to create a collection as I couldn't use First() over a variable.

 

Thanks,

J

 

 

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Watch Now

Experience what’s next for Power Apps

See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (7,309)