When I was trying the If formula under the DisplayMode I am getting the Invalid argument type, Can someone please help
Solved! Go to Solution.
Hi @OsmandFernando ,
There is something wrong with your formula, please modify it as below:
UpdateContext({EditRecord:""});
Patch(
SalesDetails_1,
LookUp(SalesDetails_1, ID = ThisItem.ID),
{ /* <-- Remove the Id and Value argument from the following {} part */
'Model No': ComboBox1.Selected,
Quantity: Value(QtyLable.Text),
'Unit Price': Value(UnitPriceLable.Text)
}
)
Set the Items property of the ComboBox1 to following:
Choices('YourSPList'.'Model No')
Please consider take a try with above solution, then check if the issue is solved.
Best regards,
Hi @OsmandFernando ,
Could you please share more details about the formula you typed within the Items property of the ComboBox1 in your Gallery?
Is there a "Id" column in your SP List, which is marked as Required field?
If there is a "Id" column in your SP List (SalesDetails_1), which is marked as Required, please consider add the Id field as argument within the '{}' part of your Patch formula:
UpdateContext({EditRecord:""});
Patch(
SalesDetails_1,
LookUp(SalesDetails_1, ID = ThisItem.ID),
{ /* <-- Remove the Id and Value argument from the following {} part */
'Model No': ComboBox1.Selected,
Quantity: Value(QtyLable.Text),
'Unit Price': Value(UnitPriceLable.Text),
Id: "Type Specific Number value for it"
}
)
If there is no "Id" column in your SP List, please make sure the Items proeprty of the ComboBox has been set to the formula I mentioned above:
Choices(SalesDetails_1.'Model No')
Please take a try with above formula, check if the issue is solved.
Best regards,
This error means you are comparing variables of different types. ID is a number type variable but it is not being compared to another number type variable here. Any idea what the EditRecord variable holds and what data type it is (e.g. string, number, boolean, record, etc.?
Hi @OsmandFernando ,
Could you please share a bit more about the EditRecord that you mentioned? Is it a Record value or a single Number value?
Do you add the Text Input box within a Gallery?
Based on the error message that you mentioned, it seems to tell that there is something wrong with the first argument of your If function. The result the ThisItem.ID formula returns a Number value, please check if the EditRecord variable is also a single number value.
If the EditRecord variable is a Record value, I think this is the issue within your app. We could not compare a single number value with a Record value directly.
I assume that the EditRecord variable is a Record, please consider modify your formula as below:
Set the DisplayMode property of the Text Input box in your Gallery to following:
If(
ThisItem.ID = EditRecord.ID,
DisplayMode.Edit,
DisplayMode.View
)
If the EditRecord is a Collection in your app, which contains only single one record, please modify above formula as below:
If(
ThisItem.ID = First(EditRecord).ID,
DisplayMode.Edit,
DisplayMode.View
)
Please consider take a try with above solution, check if the issue is solved.
Best regards,
I thought I already sent the reply on this to @mdevaney I used the following way and that resolved the formula issue, I am not sure I did the right thing.
If(Text(ThisItem.ID)=EditRecord,DisplayMode.Edit,DisplayMode.View)
But now my patch function is not working and indicating me as it has Invalid Argument. Following is the patch formula I used
UpdateContext({EditRecord:""});Patch(SalesDetails_1,{ID:ThisItem.ID},{'Model No':ModelnumberLable.Text,Quantity:QtyLable.Text,'Unit Price':UnitPriceLable.Text})
Let me explain you on what I am trying to do.
I have SP lists for, sales and sales details. Sales is to record general information on sales such as Invoice number, Customer Name, Total amount, payment mode. Sales details list is having field as below,
Here what I am trying to do is , If I want to edit any details related to a Sales Invoice I do in the way shown in the screen shot. O followed the following demo which I earlier received from here as a very valuable resolution for my earlier question.
https://www.youtube.com/watch?v=41Mpgn7svLs&t=1s
MyEditRecord variable is this - UpdateContext({EditRecord:Text(ThisItem.ID)}) - Hope I am referring to the correct one
I am very new to Powerapps but love it so much. This is my 1st detail app. I am learning while doing. I want say that I am working hard to learn more and more. Also I appreciate that if you can share any good link/s, resource/s which I can use to enhance my capacity.
Much grateful for your support @v-xida-msft @mdevaney
Osmand Fernando
Hey @OsmandFernando
Can you try to update the expression as:
UpdateContext({EditRecord:""});Patch(SalesDetails_1,LookUp(SalesDetails,ID = ThisItem.ID),{'Model No':ModelnumberLable.Text,Quantity:QtyLable.Text,'Unit Price':UnitPriceLable.Text})
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
@yashag2255 Thank you so much for your quick reply. I did that but getting an error as below,
Is this correct for the display mode of the text inputs, If(Text(ThisItem.ID)=EditRecord,DisplayMode.Edit,DisplayMode.View)
Thank you so much for the wonderful s
Hey @OsmandFernando
Can you share more details about this EditRecord variabel, based on the expression shared by you, the variabel si set to blank. WHere are you assigning values to it?
If(Text(ThisItem.ID)=EditRecord,DisplayMode.Edit,DisplayMode.View)
The above expression is valid if the EditRecord holds a text value for ID.
Regarding the error that you are getting in Patch, can you please check if you are using the correct column names and passing valid data type value to them. Based on schema share by you, Model Number seems to be a lookup but you have passed a text value for it.
You need to correct that as:
UpdateContext({EditRecord:""});Patch(SalesDetails_1,LookUp(SalesDetails,ID = ThisItem.ID),{'Model No':LookUp(Choices(SalesDetails.'Model No'), ModelNoColumn = ModelnumberLable.Text),Quantity:QtyLable.Text,'Unit Price':UnitPriceLable.Text})
Here, ModelNoColumn needs to be replaced with the name of column that holds the text as ModelnumberLable.Text
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
@yashag2255 thank you so much for your reply.
I tried but still having an issue. I did the following,
UpdateContext({EditRecord:""});Patch(SalesDetails_1,LookUp(SalesDetails_1,ID = ThisItem.ID),{'Model No':LookUp(Choices(SalesDetails_1.'Model No'), 'Model No'= ModelnumberLable.Text),Quantity:QtyLable.Text,'Unit Price':UnitPriceLable})
The name of the Model number in the SharePoint list is Model No.
The EditRecord variabel is set as below,
UpdateContext({EditRecord:Text(ThisItem.ID)}) it is set to Edit Icon
Following are the field types in the SharePoint list,
Invoice number - Drop down look up from Sales table
Model No - Drop down look up from Item master table
Quantity - Number field
Unit Price - Currency field
Thanks, Osmand
Hi @OsmandFernando ,
Is the 'Model No' column a LookUp type column in your Sales details List?
Based on the formula you provided, I think there is something wrong with it. I have made a test on my side, please consider take a try with the following workaround:
Please consider modify your Patch formula as below:
UpdateContext({EditRecord:""});
Patch(
SalesDetails_1,
LookUp(SalesDetails_1,ID = ThisItem.ID),
{
'Model No': {
Id: LookUp(ItemMasterList, ReferencedColumn = ModelnumberLable.Text, ID),
Value: ModelnumberLable.Text
},
Quantity: Value(QtyLable.Text),
'Unit Price': Value(UnitPriceLable.Text)
}
)
Note: I assume that the 'Model No' field reference the ReferencedColumn in your ItemMasterList.
Please consider take a try with above solution, then check if the issue is solved.
Best regards,
@v-xida-msft Thank you so much for your reply. Actually the code provided @yashag2255 worked for the model number. And you code also worked. But for the both I had to change the column type of Quantity and Unit price to "Text". Those were Number and Currency. Anyway it is working now. But I want to know when the column type is Number and Currency what should be the code in the Patch ?
I will mark both answers as solutions once I got a reply to this. Also I have another issue where I need support, I will search on it and then send a another new post for that.
I am so grateful to @v-xida-msft @yashag2255 @mdevaney . Thank MS for this platform.
Osmand
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