Good day,
I have my sharepoint list with the column Department being of type CHOICE.
In powerapps i am collecting the values (last line):
Collect(ColItemsToKeep,
{
Order_No: DataCardValue5.Text,
Covid_choice: DataCardValue37.Value,
Je_Respecte: DataCardValue60.Value,
EPI_ND: DataCardValue35.Text,
Acces_cabine: DataCardValue61.Value,
Je_Realise: DataCardValue104.Value,
Autres_Commentaires: DataCardValue6.Text,
Department: DataCardValue13.SelectedItems
}
);
Then i am patching some values along with the Department value collected to the sharepoint list (still last line):
ForAll(ColItemsToKeep,Patch('Take5 V1',Defaults('Take5 V1'),
{
Title: Order_No,
Covid_Choice: Covid_choice,
Je_Respecte_Les_Regles: Je_Respecte,
EPI_ND: EPI_ND,
Je_Dois_Acceder_a_la_Machine: Acces_cabine,
'Sanitize Cabin': Sanitize_cabin,
'Sanitize Keys': Sanitize_Keys,
'Autre(s) Risque(s)': Autres_risques,
'I Plan': Je_Planifie,
I_Plan_Comments: Je_Planifie_Comment,
SAFE: Je_Realise,
'General Comments': Autres_Commentaires,
Department:Department
}
));
I am however getting an error:
The type of this argument 'Department' does not match the expected type 'Record'. Found type 'Table'.
Help please...all other values are correctly being collected and patched.
Thanks.
Solved! Go to Solution.
@AOZ
Perfect! Then the Choices function will already be providing everything you need. The ONLY thing you need to change in the collect formula is to change .SelectedItems to .Selected
Because again, SelectedItems is a table, and your column is not defined to allow multiple values. Selected is a record...and it will already have the schema signature necessary to supply to your datasource when you use it to make new records in the other formula.
Your Choice column is a single selection column. You are trying to set the column to SelectedItems - which is a table.
You need to collect the value of the selection, not the table of selections.
It appears you are using a form as I see a lot of DataCardValue control names. You should really save yourself a TON of unneeded work by using the submit on the form. I know you are also doing your app for offline use, so you should be collecting records directly from the Form from the Updates property. This will have Everything in it for the record and will not only keep you from having to define all the columns but also be able to completely reduce your final patching formula down to a simple line.
Ex. : To collect the form record - Collect(ColItemsToKeep, yourForm.Updates)
then to patch - Collect('Take5 V1', ColItemsToKeep)
This would save you a ton of trouble!
I hope this is helpful for you.
Hi again! Yes i understand your point. As i new and have reached quite far in the coding...a bit difficult for me to revert back. I will keep all your precious advices for another app which i will be developing.
But for now, can you indicate how to collect the "value" and not the table of selections?
And also, good syntax for the patching?
P.S: Pens down today!
No pens...too bad! Yes, I'm all about getting people to go simple with PowerApps. It makes a world of difference and keeps traction moving with this platform.
Yes...so then your collection statement would be:
Collect(ColItemsToKeep,
{
Order_No: DataCardValue5.Text,
Covid_choice: DataCardValue37.Value,
Je_Respecte: DataCardValue60.Value,
EPI_ND: DataCardValue35.Text,
Acces_cabine: DataCardValue61.Value,
Je_Realise: DataCardValue104.Value,
Autres_Commentaires: DataCardValue6.Text,
Department: DataCardValue13.Selected.column
}
);
Since the "column" to specify in the above is unique to your combobox, you need to replace it with the appropriate name. Ex. if your Items property is Choices function bases, then replace above with Value. If it is Distinct based, then replace with Result. If it is based on a datasource, then replace with the column name you want.
For your Patch - you don't need to use patch. Collect will do what you want, create new records:
Collect('Take5 V1',
ForAll(ColItemsToKeep,
{
Title: Order_No,
Covid_Choice: Covid_choice,
Je_Respecte_Les_Regles: Je_Respecte,
EPI_ND: EPI_ND,
Je_Dois_Acceder_a_la_Machine: Acces_cabine,
'Sanitize Cabin': Sanitize_cabin,
'Sanitize Keys': Sanitize_Keys,
'Autre(s) Risque(s)': Autres_risques,
'I Plan': Je_Planifie,
I_Plan_Comments: Je_Planifie_Comment,
SAFE: Je_Realise,
'General Comments': Autres_Commentaires,
Department:Department
}
)
)
Maybe i have wrongly explained myself...i don't have the selected.column as you advised...
Here are some screenshots of the sharepoint list "Department" column...
You have explained well and I understand the issue completely. This actually nothing to do with your column, this is everything to do with the property you are selecting in your formula. You are using SelectedItems - that property is a Table of records of items selected. You need to specify the Record selected. This is in the Selected property. But then you need (depending on the Items property of the control) to specify the column of that record. This is the record as it is in your App, nothing to do with the column definition in your list.
A Choice column in SharePoint is a record. It has a Value column.
BUT, what you choose is completely dependent on the Control Items property.
So...what is your Items property on the control named : DataCardValue13 ??
@AOZ
Perfect! Then the Choices function will already be providing everything you need. The ONLY thing you need to change in the collect formula is to change .SelectedItems to .Selected
Because again, SelectedItems is a table, and your column is not defined to allow multiple values. Selected is a record...and it will already have the schema signature necessary to supply to your datasource when you use it to make new records in the other formula.
OK thanks - but it still says that the function Collect has some invalid arguments.
Incompatible type. The type you're trying to put into a collection has a type that's not compatible with the collection.
Collect(ColItemsToKeep,
{
Order_No: DataCardValue5.Text,
Covid_choice: DataCardValue37.Value,
Je_Respecte: DataCardValue60.Value,
EPI_ND: DataCardValue35.Text,
Acces_cabine: DataCardValue61.Value,
Sanitize_cabin: DataCardValue11.Value,
Sanitize_Keys: DataCardValue12.Value,
Sanitize_vehicle: DataCardValue2.Value,
Sanitize_knobs: DataCardValue1.Value,
Sanitize_int_ext: DataCardValue3.Value,
Sanitize_others: DataCardValue4.Value,
Compétences: DataCardValue42.Value,
Manuels_Techniques: DataCardValue43.Value,
Instructions: DataCardValue44.Value,
Outils: DataCardValue45.Value,
EPI_Pas_Dispo: DataCardValue46.Value,
Sortie_secours: DataCardValue47.Value,
Places: DataCardValue48.Value,
Environnement: DataCardValue49.Value,
Machine_pas_propre: DataCardValue50.Value,
Autres: DataCardValue7.Value,
Des_Machines: DataCardValue51.Value,
Dautres_Personnes: DataCardValue52.Value,
De_Lelectricite: DataCardValue53.Value,
Des_Bruits: DataCardValue54.Value,
Des_charges: DataCardValue55.Value,
Produits_chimiques: DataCardValue56.Value,
des_vehicules: DataCardValue57.Value,
la_hauteur: DataCardValue59.Value,
Autres_risques: DataCardValue58.Value,
Je_Planifie: DataCardValue16.Value,
Je_Planifie_Comment: DataCardValue38.Text,
Je_Realise: DataCardValue104.Value,
Autres_Commentaires: DataCardValue6.Text,
Department: DataCardValue13.Selected
}
);
Yep...just another "plus one" for why not to do this kind of thing! It's not only way too much work, but it is fraught with issues and compatibility.
Now (off the soap box), since you're sticking with this, the question is with the issue that the error is related to - is is in fact complaining about the Department column? Remove that from your collect formula and see if the error goes away. If it doesn't, then you need to find which column it is complaining about.
If it does go away, then you need to look at EVERY other place that you are doing anything with that collection in your app to see if you are setting that column to a different type.
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