Hi there,
Having some issues with LastSubmit variable being passed over to another form that is using a different DataSource.
I have two Datasources and three forms. Two of the forms use the same datasource and the other form uses a different datasource. I set a variable of the first form to get the LastSubmit.ID of that form and then I use that for the other form that uses a different datasource. FormMode = New, a new form is submitted at the Personal Info screen. Then the user continues to fill out the form and depending on their answers, it will either take them to another screen that uses the third form that uses a different datasource OR it will use the answers they submitted in the subsequent screens and put their answers on a form that uses the same datasource as the first submitted form that is housed on its own screen. The problem is, that when the user attempts to enter their information and submit the thrid form, the column I try and match on is being set to 0 instead of the ID of the first submitted form, which should be using the variable that I set on the first SubmitForm button.
**Note I am no longer getting the error message that is in the GIF.**
Here is a link to the GIF workflow for this app.
https://streamable.com/k4seli
Solved! Go to Solution.
@WarrenBelz - I believe I didn't Publish your changes in the app, so I republished the app and ran it again with different results from above.
1. New Form > Fill out fields in Personal Info Screen > Submit > ScreeningForm is submitted Successfully.
(Confirmed validation as I receive an email notifying me that it has been successfully submitted)
2. Continue onto the QuestionsForm > Fill out fields in the corresponding fields that DO NOT take me to the Contact Tracing Screen > Submit > ERROR: There was a problem saving your changes. The data source may be invalid.
Going to wait to hear back from you so we can stay focused on one issue at a time.
This is now getting way beyond the scope of your question which was about the LookUp not returning the value you wanted. We are now debugging a program that I have cannot see or understand all the connections and logic. So please focussing on that matter, does setting the Variable at both Gallery OnSelect and Form OnSuccess as per my last post set the variable to the ID you need to both set new records and display existing ones linked to the current record?
I am happy to help further, but I may not have the time for a little while and this may have to be a Teams screen share. What time zone are you in?
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
@WarrenBelz - My apologies.
"...does setting the Variable at both Gallery OnSelect and Form OnSuccess as per my last post set the variable to the ID you need to both set new records and display existing ones linked to the current record? " - I added two text fields, one on the Personal Info screen and the other on the Screening Questions screen, changed the Default = lastID. The Personal Info screen is grabbing the lastID from the BrowseGallery1_1 however, after I submit the Form from the Personal Info screen and navigate to the Screening Questions screen, the lastID is showing No value
Also, I am in the CST time zone. I know you're in Queensland, Australia...would love to do a Teams session if possible.
What form is on the Personal Info Screen? As I mentioned, you need to put this on the OnSuccess
Set(lastID,Self.LastSubmit.ID)
then it will set lastID to the ID of the form it just submitted. You are 16 hours behind me, meaning it is currently just before 3am?
The critical thing now is to get lastID to always reflect the ID of the current item being worked on. All should be straight forward after that. You should not need Variables for the state of the form - you can call EditForm() or NewForm() directly depending on the need at the time.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
@WarrenBelz, - The form is called the ScreeningForm. I entered your code from above to the OnSuccess of that form, (Not sure this matters) BUT I still have code on the Submit.OnSelect on the Personal Info Screen that has the ScreeningForm on it that may be fighting the lastID variable.
Submit.OnSelect
SubmitForm(ScreeningForm);
Reset(Status_Dropdown);
Reset(Reason);
Reset(Type);
Reset(EmergencyContact);
Reset(DatePicker2);
Reset(ProjectName_Dropdown);
Reset(ProjectNumber);
Reset(RoleDropDown);
Reset(PhoneNumber);
Reset(WorkerName);
Reset(CompanyName);
Reset(Emergency_Contact_Number);
Reset(office_jobsite);
Reset(office);
Reset(other_craft_field);
Reset(Non_Clayco_Dropdown);
Set(lastID,ScreeningForm.LastSubmit.ID);
Set(LastContactID,ScreeningForm.LastSubmit.ID);
ResetForm(ScreeningForm);
If(Reason.Selected.ProductName="Travel" || ReasonView.Text= "Travel", Navigate(Travel_Info),Navigate('Screening Questions'));
Set(varMode,"New");
Refresh('[dbo].[COVID_Screening_Form]');
Should I remove that code and keep your OnSuccess code you told me to enter?
Thanks.
Updated the Submit.OnSelect and commented out the code...still isn't passing the lastID over when navigating from the Personal Info screen over to the Screening Questions screen.
Set(varLoad,true);
SubmitForm(ScreeningForm);
If(Reason.Selected.ProductName="Travel" || ReasonView.Text= "Travel", Navigate(Travel_Info),Navigate('Screening Questions'));
/*Set(varMode,"Edit");*/
Reset(Status_Dropdown);
Reset(Reason);
Reset(Type);
Reset(EmergencyContact);
Reset(DatePicker2);
Reset(ProjectName_Dropdown);
Reset(ProjectNumber);
Reset(RoleDropDown);
Reset(PhoneNumber);
Reset(WorkerName);
Reset(CompanyName);
Reset(office);
Reset(office_jobsite);
Reset(other_craft_field);
//Set(lastID,ScreeningForm.LastSubmit.ID);
//Set(lastID,QuestionsForm.LastSubmit.ID);
//Set(lastID,Contact_Tracing_Form.LastSubmit.ID);
ResetForm(ScreeningForm);
Refresh('[dbo].[COVID_Screening_Form]');
Set(varLoad,false);
Yes, setting the Variable needs to go on OnSuccess - on a new form that is the only way you can catch it other than referring to LastSubmit later on. The rest does not matter.
Can you please send me your email via Private Message - I may be available sometime tomorrow afternoon (my time), so it will be later Monday night for you.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Hi @borowiakn ,
As per our Teams session, can you please accept this as solved so it can be closed and allow other people to find it more readily.
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