I'm using a Form for screen 1 and a Data Table for screen 2! I cannot collect the fields from Screen 1 into Screen 2 and then publish them as one record in Sharepoint!
HI @razken88
You actuaqlly can achieve this, but I'll need more details about what exactly you are trying to accomplish. Based on your description, here's a potential solution:
1. Store Form Data from Screen 1: When navigating from screen 1 to screen 2, save all the form data from screen 1 into a collection or variable. For example:
Collect(Screen1Data, {Field1: DataCardValue1.Text, Field2: DataCardValue2.Text})
2. Store Form Data from Screen 2: Do the same for the form data on screen 2. For example:
Collect(Screen2Data, {Field3: DataCardValue3.Text, Field4: DataCardValue4.Text})
3. Combine Data from Both Screens: Combine the data from both screens into a final collection. For example:
ClearCollect(FinalData, Screen1Data, Screen2Data)
4. Patch the Final Collection to SharePoint: Patch this final collection into the SharePoint list. For example:
Patch(SharePointList, FinalData)
I hope this explanation helps. However, we need more information about your current setup and what you want to achieve to provide a more precise solution.
Thanks for your response. It does help clarify the collection part of the data as one record into SharePoint. However, I'm still looking for clarification on navigating the multiple screens before creating the one record for Sharepoint. The query I currently have is throwing errors
As I said in my previous response, Ill need more details to help you like the actual error you are facing.
Here's my query:
Thanks for sharing more details. First, there's a small error in your code:
Navigate(MOTORMAKE, ScreenTransition.Cover, {
HeaderStoreName: ThisItem.StoreName,
HeaderStoreNumber: ThisItem.StoreNumber,
});
You have an extra comma after ThisItem.StoreNumber.
Now, I think I understand your requirement better, but there's still a part that I'm not clear on. Let's say you have a form called Form(MotorMake) on Screen1, which we'll call the MotorMake screen. If you want to jump to Screen2, the MotorBrand screen where the table is, your code should point to the MotorBrand screen, not the MotorMake screen.
Also, about the MotorBrand screen. Here's what I'm trying to understand, You collect information from MotorMake and then pass that information in context variables to the MotorBrand screen, right?
Is the information in the MotorBrand table filtered based on the values of these context variables?
So, the information put in Screen1 is not directly updated but just captured to use in Screen2?
If that's correct, the problem might be with your navigate formula. Please try this:
Navigate(MotorBrand, ScreenTransition.Cover, {
HeaderStoreName: ThisItem.StoreName,
HeaderStoreNumber: ThisItem.StoreNumber
});
Make sure the screen you're navigating to is MotorBrand, not MotorMake.
If my response resolved your issue, please feel free to mark it as the solution by clicking "Accept as solution." This helps others find the answer more easily. If you found the content helpful in any other way, a "Thumbs Up" would be greatly appreciated. Thank you! 😁
I really appreciate your input! The two screens Motor Brand and Motor Make, mirror a manual form. MotorBrand has the Header Details, while MotorMake has the Liner details, which is entered as a table. The two screens are collected and published as One record in SharePoint. I did change the query to MotorBrand and it now recognizes it, however it doesn't recognize any of these field items '
HeaderStoreName: ThisItem.StoreName
I rewrote the screen fields with the prompt that started with the field name and the prompt included the DataCard for screen1, the error is now gone and switched to screen 2. The issue is now screen 2 that starts to throw an error with the MotorMake(Form from Screen 1)
This is the query on the Screen 2 button, it throws the following error: 'Unexpected characters. The formula contains 'Control' where 'indent' is expected'
-------The Query for collecting Screen1 &2 then creating one record is as written below:
Set(MOTORMAKE, MOTORMAKE.Updates);
ClearCollect(DataTableItems, DataTable1.AllItems);
ClearCollect(MergedCollection,
{
HeaderStoreName: StoreName_DataCard1.Selected,
HeaderStoreNumber: StoreNumber_DataCard1.Selected.Value, {
TxtDiscountAmount: ThisRecord.DiscountAmount,
ItemNumber: ThisRecord.ItemNumber, }
)
}
);
Patch('Order UAT', Defaults('Order UAT'),
{
StoreName: First(MergedCollection).HeaderStoreName,
StoreNumber: First(MergedCollection).HeaderStoreNumber,
LineItems: First(MergedCollection).LineItems
}
);
Hi @razken88
It looks like the error in your code is due to improper placement and nesting of curly braces {} and the incorrect usage of the ForAll function within the ClearCollect function. Here’s how you can correct your code:
Set(MOTORMAKE, MOTORMAKE.Updates);
ClearCollect(DataTableItems, DataTable1.AllItems);
// Create MergedCollection to combine Screen1 & Screen2 data
Clear(MergedCollection);
Collect(MergedCollection,
{
HeaderStoreName: StoreName_DataCard1.Selected,
HeaderStoreNumber: StoreNumber_DataCard1.Selected.Value
}
);
ForAll(DataTableItems,
Collect(MergedCollection,
{
TxtDiscountAmount: ThisRecord.DiscountAmount,
ItemNumber: ThisRecord.ItemNumber
}
)
);
// Patch the collected data to 'Order UAT'
Patch('Order UAT', Defaults('Order UAT'),
{
StoreName: First(MergedCollection).HeaderStoreName,
StoreNumber: First(MergedCollection).HeaderStoreNumber,
LineItems: DataTableItems // Adjust this part based on your schema
});
This should resolve the syntax errors and correctly merge the data from Screen1 and Screen2 into a single collection before patching it to Order UAT.
If my response resolved your issue, please feel free to mark it as the solution by clicking "Accept as solution." This helps others find the answer more easily. If you found the content helpful in any other way, a "Thumbs Up" would be greatly appreciated. Thank you!
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