The code I am using - kind of copied and modified from someone else's code I found online - which is to save changes made to editable field in PowerApps back to the SQL table - is not working. I tested by editing the field "Meeting Notes" for one project, and then clicked on the Save icon, then went to check the SQL table, and the change was not there.
Below is the screenshot of the PowerApps. The circled box is the editable field "Meeting Notes", which is a TextInput.
When user makes changes to that field, and then clicks on the Save icon, the code is set to:
OnSelect = Patch(ProjectTrackerPowerApps, First( Filter(ProjectTrackerPowerApps, ProjectTrackerID=Value(First([@PowerBIIntegration].Data).ProjectTrackerID)),{'Meeting Notes':TextInput1.Text)
(p.s. "ProjectTrackerPowerApps" is the table of the SQL table)
Thanks!
Solved! Go to Solution.
@Anonymous
This makes no sense!! We're right back to the start!
If you change that formula to:
Patch(ProjectTrackerPowerApps,
{ProjectTrackerID=450,
'Meeting Notes': TextInput1.Text
}
)
Does that work?? My guess is no because we used that before. And that is the exact same formula that you had in the troubleshooting button with the exception of it getting the notes from the TextInput1, which is all perfectly fine.
@Anonymous
SO ... to sum it up for anyone following this thread, there were three things wrong:
1) My mistake on copying the original formula and modifying it and not changing the equal to a colon (see formula below)
2) The ProjectTrackerID was *really* being passed as Text and needed to be converted to a value.
3) There was no TextInput1 control in the screen. It was 'Meeting Notes' (yes, the name of the control, the same as the column name.
The final formula was:
With({_ID: Value(First([@PowerBIIntegration].Data).ProjectTrackerID)
},
Patch(ProjectTrackerPowerApps,
{ProjectTrackerID:_ID,
'Meeting Notes': 'Meeting Notes'.Text
}
)
)
Problem resolved...patch is working properly now.
@Anonymous
No problem at all. I am glad we gave up on the back and forth and went screen-share. That made all the mysteries disappear.
Have a great weekend!
@Anonymous
You have a syntax error in your formula. Plus, you would want to always avoid First(Filter as it creates a performance issue in the app. The LookUp function performs the same process without the performance hit.
The formula should be:
Patch(ProjectTrackerPowerApps,
LookUp(ProjectTrackerPowerApps,
ProjectTrackerID=Value(First([@PowerBIIntegration].Data).ProjectTrackerID)
),
{'Meeting Notes':TextInput1.Text}
)
This can also be changed to the following:
Patch(ProjectTrackerPowerApps,
{ProjectTrackerID=First([@PowerBIIntegration].Data).ProjectTrackerID,
'Meeting Notes':TextInput1.Text
}
)
Although you might not be hitting the right record based on looking at the First of the integration data, but that is hard to tell from your description and without knowing your app more.
I hope this is helpful for you.
Thanks @RandyHayes . I don't think this will work because I just noticed that one test record where I have put "This is test notes!" in the Meeting Notes field, that value is not showing up in the Meeting Notes field of the Powerapps. (Pls see screenshot). The Meeting Notes field in the Powerapps is a textinput component and the code is set to:
Default = First([@PowerBIIntegration].Data).'Meeting Notes'.
Can you please help me correct this code so that the Meeting Notes shows up, and then I can test the Save code you kindly shared. Thank you!
@Anonymous
Well I feel your first issue is with First. Why are you just working with the First record? It seems you have a gallery there with multiple items in it.
Can you clarify?
Being 2 weeks old into PowerApps, when I created my PowerApps form and integrated into the PBI report, I kept having the "Getting your data" message hanging. Then after some searching online, I came across this solution: https://www.c-sharpcorner.com/forums/how-to-solve-the-getting-your-data-error-message-in-powerapps and used the code the person suggested and after I did, the data appeared when I opened the PowerBI report and the PowersApps loaded. So I was happy with that. But clearly, if that created a different issue, then I would want to correct that.
Can you please advise (suggest solution or code)?
I have been through so many video tutorials and forums and what not, and it's really difficult with no background in short time to fix things (I have a project deadline). Thank you Randy!
@Anonymous
Well let's start with your Gallery then...what is the Items property of your Gallery?
I don't have a Gallery. I tried working with a Gallery because so many tutorials show that - but it didn't work for me in the sense that the project selected in the PowerBI wasn't filtering in the PowerApps at all. Then when I took a different approach - no Gallery, just adding labels to the Tree View (see attached screenshot), I managed to at least get the project to filter.
If possible, can we work with this Tree View because the filtering works. I just need the Project Name and Meeting Notes field values to display properly in the front end - ProjectTrackerID and Project ID display but not the other 2. This is a separate, but clearly related, issue I have also asked in separate thread: https://powerusers.microsoft.com/t5/Building-Power-Apps/Label-value-not-displaying/m-p/1660884#M4229...
Thanks Randy.
@Anonymous
As I looked at your picture, it appears that you have a gallery as you offer a selection of an item. Upon further looking at it, I realize that you are actually showing your PowerBI interface with your app next to it as it comes up.
Yes, so if you are only concerned with one record in your app as it is passed from the integration, then First is fine.
Let's focus on one thing though to start...the meeting notes.
Change the Default property to:
LookUp(ProjectTrackerPowerApps,
ProjectTrackerID=First([@PowerBIIntegration].Data).ProjectTrackerID,
'Meeting Notes'
)
What is the result of that?
@RandyHayes You are a hero !!! It worked! Meetings Notes show up now! (see screenshot). Thank you!!!
Now do you know why Project Name doesn't show up?
The code for Project Name is:
Text = First([@PowerBIIntegration].Data).'Project Name'
It's the same as for ProjectTrackerID and Project ID, but those 2 show up and Project Name doesn't.
Will also try the Save code now.
YOU ARE GODSEND! (Literally)
@Anonymous
Glad to help!! 🙂
So let's change the Text property of the Project Name to this:
LookUp(ProjectTrackerPowerApps,
ProjectTrackerID=First([@PowerBIIntegration].Data).ProjectTrackerID,
'Project Name'
)
You'll notice that what is different with these is that we are looking up the actual columns directly from the datasource...not from the integration. The only thing we are getting from the integration is the ProjectTrackerID...which is all we need.
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!
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
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.
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