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

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

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

1 ACCEPTED SOLUTION

Accepted Solutions
PowerAppBCS
Frequent Visitor

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.

View solution in original post

9 REPLIES 9
v-xida-msft
Community Support
Community Support

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:5.JPG

 

6.JPG

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

 

 

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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.

Screenshot (87).png

 

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)

Screenshot (88).png

 

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

 

Thanks

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

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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:

Screenshot (90).png

 

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

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.

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

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

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:

Screenshot (95)_LI.jpgScreenshot (96)_LI.jpg

 

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:

Screenshot (97).png

 

Thanks

PowerAppBCS
Frequent Visitor

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.

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

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Solution Authors
Top Kudoed Authors
Users online (1,819)