Dynamics 365 app - I have a lookup field in D365 which is not allowing PowerApp to save, how to fix?

[PowerAppBCS]

I have 2 entities in D365, "Care Card" and "Opportunity". There is a lookup field in Care Card called "Project" that points to Opportunity. 

I have created the app in PowerApps with the D365 Care Card data. For the browse screen and detail screen Project shows as a GUID, the way to sort this is to change the Project fields Text property to "LookUp(Opportunities,opportunityid=ThisItem.Project,name)"

Where I run into an issue is on the Edit Screen. As shown in Screenshot 1 (attached) when I select the DropDown of the Project DataCard I can change the Primary Text and Search Field to match the correct fields in Opportunities. As shown in Screenshot 2 the lookup dropdown then works exactly how I want it to. But when I try to save (as in Screenshot 3) I get the error "There was a problem saving your changes. The data source may be invaled." There is also an error on the tick Accept icon "Expected dataEntityRecord for navigation column".

I am pretty certain that it is the Project lookup that is causing the error and not allowinmg it to save, I have tested it a number of different ways to make sure. Also the Care Card form in D365 works perfectly, I am just trying to replicate it in PowerApps.

Any help is greatly appreaciated.

Thanks

[v-xida-msft]

Hi @PowerAppBCS,

Do you want to save the LookUp field in your Edit form into your D365 Entity ('Care Card')?

The user @Yann_SP has faced same issue with you, please check the solution he provided within the following thread:

https://powerusers.microsoft.com/t5/General-Discussion/Form-not-saving-to-Dynamics-when-using-lookup...

In addition, as alternative solution, you could also consider take a try to submit your form data into your 'Card Card' Entity using Patch function instead of SubmitForm function.

I have made a test on my side, please take a try with the following workaround:

Firstly, please turn off/disable the "Use column display names" option and "Use GUID data types instead of strings" option within Advanced settings of App settings of your app.

Within the Edit screen, add a "Patch" button, set the OnSelect property to following:

Patch(
    Employees, 
    Defaults(Employees), 
    {
        new_name: DataCardValue13.Text, 
        _new_account_value: DataCardValue16.Selected.accountid  /* <-- DataCardValue16 represents the Combo Box control within the Account Data card*/
    }
)

Note: The Account column is a LookUp column in my Entity (Employees). The '_new' represents the prefix of the column name in my Entity.

On your side, please consider modify your formula within the "Submit" button to following:

Patch(
    'Care Card', 
     Defaults('Care Card'), 
     {
        prefix_project_value: YourProjectComboBox.Selected.opportunityid, /* <-- On your side, the opportunityid may be bcs_projectid */
        prefix_action: DataCardValue2.Text,
        ...
        prefix_recommandation: DataCardValue4.Text,
        ...
     }
)

Best regards,

Kris

[PowerAppBCS]

Hi @v-xida-msft,

Thanks for the reply. 

Yes I want to save the LookUp field to the D365 Entity ("Care Card"). In D365 I have a form "New Care Card" which has the "Project" LookUp and other fields (Action, Recommendation, etc) and saves in the "Care Card" entity, I want to replicate this in PowerApps. 

I have tried the solution from @Yann_SP previously but couldn't get it to work.

I have added a button and set a Patch function for the OnSelect.

I am running into an error because of incompatible data types as in screenshot below (LookUp field is the field causing error as all other fields work without it)

Do I have the Patch function set up incorrectly or do I need to convert the data types?

Thanks

[v-xida-msft]

Hi @PowerAppBCS,

Based on the error message that you mentioned, I think there is something wrong with the value you provided for the bsc_Project column within your Patch formula.

The bsc_Project column is required to provide a record value, but you provided a Text value.

Please modify your Patch formula as below:

Patch(
         'Care Cards',
         Defaults('Care Cards'),
         {
             bsc_Project_value: DataCardValue25.Selected.bcs_projectid, /* Please type bsc_Project_value column rather than bsc_Project column */
             bsc_action: DataCardValue15.Text,
             bsc_issueobservation: DataCardValur26.Text,
             bsc_recommendation: DataCardValue27.Text
         }
)

Note: You could find the bsc_Project_value property via property selector (.) after the 'Care Cards' data source. e.g.

'Care Cards'.

the avaiable properties would show up after the proprety selector (.).

Best regards,

Kris

[PowerAppBCS]

Hi Kris,

I found what I think is the correct _bcs_project_value:

Patch(
    'Care Cards',
    Defaults('Care Cards'),
    {
        _bcs_project_value: DataCardValue25.Selected.bcs_projectid,
        bcs_action: DataCardValue15.Text,
        bcs_issueobservation: DataCardValue26.Text,
        bcs_recommendation: DataCardValue27.Text
    }
)

The LookUp field still does not save (note the other fields do work by themselves). This shows up with no errors when I first enter it but once I test it out it shows with an error:

The error is "The requested operation is invaled. Server response: Bad request - error in query syntax."

I think this is getting much closer to a solution but I am not sure why the error is happening.

Thanks

[v-xida-msft]

Hi @PowerAppBCS,

Currently, I could not reproduce your issue on my side.

Please check if you have turned off/disabled the "Use column display names" option and "Use GUID data types instead of strings" option within Advanced settings of App settings of your app (Please turn off the two options).

The user @MikeRogers has faced same issue with you, please check the response within the following thread:

https://powerusers.microsoft.com/t5/Building-Flows/Error-creating-new-Opportunity-in-Dynamics/td-p/6...

In addition, please also check if the result the DataCardValue25.Selected.bcs_projectid formula within your Patch function returned is a valid GUID string value.

[Anonymous]

Hi @PowerAppBCS thanks for posting in the community. Have you been able to solve your issue? Please let me know if the above response from CST has helped as well. 

@Anonymous

[PowerAppBCS]

Hi @v-xida-msft & @Anonymous,

I have not been able to solve this issue yet.

Both the "Use column display names" option and "Use GUID data types instead of strings" options are turned off.

For the edit form there are 2 Different fields available for Project:

The first field is a dropdown that displays all the projects. The second field shows the selected project as a GUID (I used a LookUp function to show the project name). I have underlined in red the datafield for each. 

I have tried several different Patch functions but cant find one that works. Can you think of a different way to do it with the second project field potentially? Note that when I change the project dropdown it does not change the second project field:

Thanks

[PowerAppBCS · Accepted solution]

I have been able to get this worked by using Common Data Service as the data source instead of using Dynamics 365 as the data source.

[rkaur3]

Had been just struggling for this. and strangely the fix was to replace the connector coz Dynamics connector doesn't support it... gosh !