Hi All, i am just stuck with this form as i am new to this platform.
here i have created the form and to the submit button, i coded in such a way to filter submitted Assets gets into collection. i have connected my sharepoint list now. how do i send the data from my collection to sharepoint list by filtering only the submitted one.
My collection name is 'AssetUtilisation', sharepoint name is 'Utilisation East'
Hi @ahamedafridi18 ,
Identify the Condition for Submitted Items: Determine what makes an item in 'AssetUtilisation' considered as 'submitted'. This could be a specific column or status.
Use the Patch Function: Iterate over the 'AssetUtilisation' collection and use the Patch function to add items to the SharePoint list.
Example Code:
ForAll(
Filter(AssetUtilisation, YourConditionHere),
Patch(
'Utilisation East',
Defaults('Utilisation East'),
{
Title: TitleColumn, // Replace with actual column names and values
// Other columns...
}
)
)
Replace YourConditionHere with the condition that identifies a submitted item and map the column names and values from your collection to the corresponding fields in your SharePoint list.
Note: Make sure the column names used in the Patch function match those in your SharePoint list.
Best Regards,
Hassan Raza
Thanks for the quick reply Hassan, the condition i used was Set(testJSON,JSON(RemoveIf(AssetUtilisation, Submit <> "Submitted")));
so i had a submit: Sumitted in my form, so once they check and select confirm it assumes as submitted but they need to select the submit button to add the form into collection.
so yeah, after adding the condition i still see error
Hi @ahamedafridi18 ,
Follow these steps:
Check the Condition: Ensure that the condition used in the Filter function correctly identifies items marked as "Submitted". The Set(testJSON, JSON(RemoveIf(AssetUtilisation, Submit <> "Submitted"))); command removes non-submitted items from the collection. Make sure that the 'Submit' field exists and is correctly populated in the 'AssetUtilisation' collection.
Verify Data Types: Ensure that the data types in your collection match those in the SharePoint list. Mismatches in data types (e.g., text vs. number) can cause errors.
Examine Patch Function: Ensure that the Patch function is correctly structured and that the field names used in the Patch function match exactly with those in the SharePoint list. Pay special attention to any complex fields like Choice, Lookup, or Person.
Check for Errors in PowerApps: Sometimes the error message provided by PowerApps can give clues about what's wrong. If you can provide a text description of the error message, it might help in diagnosing the issue.
Test with a Simplified Patch: Try using the Patch function with a simplified dataset or fewer fields to see if the basic functionality works. This can help isolate the problem.
If you provide more specific information about the error message or the structure of your PowerApps collection and SharePoint list, I may be able to offer more targeted advice.
Best Regards,
Hassan Raza
So yeah, i have applied the code here on the submit button. The error its showing is 'This function cannot operate on same data source that is used in filter.
previously i had - Set(testJSON,JSON(RemoveIf(AssetUtilisation, Submit <> "Submitted")));
this just remove the assets which is not been selected.
So basically, i need to only the summitted assets to to be sent to SharePoint once they click 'submit fleet' button.
Hi @ahamedafridi18 ,
Create a separate collection specifically for the items you want to patch to SharePoint. This can be done right before the patch operation. For example:
ClearCollect(ToPatchCollection, Filter(AssetUtilisation, Submit = "Submitted"));
ForAll(ToPatchCollection, Patch('Utilisation East', Defaults('Utilisation East'), {Title: TitleColumn /* other columns */ }));
If the AssetUtilisation collection is not large, you might patch directly from it without using Filter in the same function:
ForAll(AssetUtilisation, If(Submit = "Submitted", Patch('Utilisation East', Defaults('Utilisation East'), {Title: TitleColumn /* other columns */ })));
If the first method causes performance issues, consider storing the filtered results in a variable first and then using that variable in the Patch function:
Set(VarToPatch, Filter(AssetUtilisation, Submit = "Submitted"));
ForAll(VarToPatch, Patch('Utilisation East', Defaults('Utilisation East'), {Title: TitleColumn /* other columns */ }));
The key here is to ensure that the Filter and Patch operations are not directly nested or applied on the same data source in the same formula. By separating these operations, you should be able to avoid the error and achieve the desired functionality.
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