Hi Experts,
I am getting the below error in my formula, not sure what i am missing here
Patch('VarianceData',First(Filter('VarianceData','EmailAdress'=lbl_useremail.Text)),{Comments:drp_Comments.Selected.Value,Comments:txt_comments.Text});
UpdateContext({showsuccess:true});
Navigate(Screen2)
Solved! Go to Solution.
Just take it out
or just put
Comments:"test"
temporarily.
If "test" works but needs to be changed to the actual value of a Form control:
Look in the Canvas App form for the name of the correct control and just use that. You will need to just look at each control until you find the one that makes sense. Just click on it and then look at the Tree view on the left side, or look on the top right side as well, see what the name of the Control is.
Example:
1. I click a Control below that looks like it might be the one I am looking for.
2. Then I look at one of the boxed red areas to see the name is Label1 and that's how I can find the name of a Control.
3. After I found the right one, I can replace txt_comments.Text with Label1.Text (but if you literally use Label1 instead of txt_comments it probably won't work, look for the actual name of your Control and makes sure it's the right one that has the right information you need to put in the Comments column)
See if it helps @vjnvinod
Patch
(
'VarianceData'
,First(Filter('VarianceData','EmailAdress'=lbl_useremail.Text))
{
Comments:drp_Comments.Selected.Value
,Comments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
1. In the above, you have Comments defined twice, you can't do that, change it to
{
Comments:drp_Comments.Selected.Value
,Another_Comments:txt_comments.Text
}
Replace Another_Comments above as appropriate or use Comments: only once, e.g.
{
Comments:drp_Comments.Selected.Value
}
I also recommend rewriting the formula like this:
Patch
(
'VarianceData'
,LookUp('VarianceData','EmailAdress'=lbl_useremail.Text)
,{
Comments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
or even better, like this:
With
(
{_myRecord: LookUp('VarianceData','EmailAdress'=lbl_useremail.Text) }
,Patch
(
'VarianceData'
,{
ID:_myRecord.ID
Comments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
)
If 'VarianceData' is not a standard SharePoint List. then replace ID in the above with the primary column of your 'VarianceData' data source. The primary column or primary key uniquely identifies all the Records in a Table.
If you don't like the With formula, you can do it like this:
Patch
(
'VarianceData'
,{
ID:LookUp('VarianceData','EmailAdress'=lbl_useremail.Text).ID
Comments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
However, if you'll use any other fields from the LookUp I recommend keeping the With version, for example:
With
(
{_myRecord: LookUp('VarianceData','EmailAdress'=lbl_useremail.Text) }
,Patch
(
'VarianceData'
,{
ID:_myRecord.ID
Comments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
UpdateContext({currentRecordColumn3:_myRecord.Column3});
//The With avoids having to repeat the LookUp formula again - without the With you have to write the above line as //UpdateContext({currentRecordColumn3:LookUp('VarianceData','EmailAdress'=lbl_useremail.Text).Column3});
Navigate(Screen2)
)
See if this helps as well @vjnvinod
Note that in both the version you gave, and the above, a new record is created if the Filter, LookUp, etc. has no match. If this is intended behavior, then that is fine.
If that is not intended behavior,
then you may want to do this instead if you want to avoid creating a new record in case of no match:
With
(
{_myRecord: LookUp('VarianceData','EmailAdress'=lbl_useremail.Text) }
,If
(
IsBlank(_myRecord)
,Notify("No VarianceData found with email address " & lbl_useremail.Text,Error)
,Patch
(
'VarianceData'
,{
ID:_myRecord.ID
Comments:txt_comments.Text
}
);
)
UpdateContext({showsuccess:true});
Navigate(Screen2)
)
i am still getting the error, when hoover its says some unexpected character
see the formula below, basically i have one dropdown and 1 text comment for users to click on submitt button
Patch
(
'VarianceData'
,First(Filter('VarianceData','EmailAdress'=lbl_useremail.Text))
{
Comments:drp_Comments.Selected.Value
,OtherComments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
yes below are the 2 fields in sharepoint list which i intend to update, can you recommend a formula?
please note that Comments is a dropdown combo box
and Othercomments is a text box
Missing a comma before the opening curly brace
Patch
(
'VarianceData'
,First(Filter('VarianceData','EmailAdress'=lbl_useremail.Text))
,{
Comments:drp_Comments.Selected.Value
,OtherComments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
Note that the above only works without error if OtherComments exists as a column in VarianceData
see the error below, there is some issue with txt_comments
here is what i have used based on above thread
Patch(VarianceData,First(Filter(VarianceData,EmailAdress=lbl_useremail.Text)),{Comments:drp_Comments.Selected.Value,OtherComments:txt_comments.Text});
UpdateContext({showsuccess:true});
Navigate(Screen2)
@vjnvinod wrote:
yes below are the 2 fields in sharepoint list which i intend to update, can you recommend a formula?
please note that Comments is a dropdown combo box
and Othercomments is a text box
A Drop down Control and a Combo box Control are not the same thing.
If Comments is a Combo box control mapped to a SharePoint Choice Column that allows multiple selections you may want to use drp_Comments.SelectedItems if you want all selected choices rather than only the last selected choice:
Patch
(
'VarianceData'
,First(Filter('VarianceData','EmailAdress'=lbl_useremail.Text))
,{
Comments:drp_Comments.SelectedItems
,OtherComments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
If you get an error, replace drp_Comments.SelectedItems with drp_Comments.Selected.Value - maybe it's just a Drop down control so it can have only one Selected value anyway then if it's a Drop down control.
If it's a SharePoint List I recommend writing like this if possible:
With
(
{_myRecord:LookUp('VarianceData','EmailAdress'=lbl_useremail.Text)}
,Patch
(
'VarianceData'
,First(Filter('VarianceData','EmailAdress'=lbl_useremail.Text))
,{
ID:_myRecord.ID
,Comments:drp_Comments.SelectedItems //or use drp_Comments.Selected.Value
,OtherComments:txt_comments.Text
}
);
UpdateContext({showsuccess:true});
Navigate(Screen2)
)
To avoid creating new values ever, do this instead:
With
(
{_myRecord: LookUp('VarianceData','EmailAdress'=lbl_useremail.Text) }
,If
(
IsBlank(_myRecord)
,Notify("No VarianceData found with email address " & lbl_useremail.Text,Error)
,Patch
(
'VarianceData'
,{
ID:_myRecord.ID
,Comments:drp_Comments.SelectedItems //or use drp_Comments.Selected.Value
,OtherComments:txt_comments.Text
}
);
)
UpdateContext({showsuccess:true});
Navigate(Screen2)
)
See if it helps @vjnvinod
@vjnvinod wrote:
OtherComments:txt_comments.Text
txt_comments may not exist as a name of a Control in your app.
Double check it.
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