cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
sb92
Helper I
Helper I

OnSuccess not writing masterID column to SPO list

I have an app that reads and writes to 2 lists - one is called hazardmaster and the other hazarddetails.

I can get the app to simultaneously create a new list item to hazardmaster and submit a collection of items for hazarddetails that are given the masterid of the last submitted item id of hazardmaster. So that works fine, but:

I also tried to create a button and form that allows the user to create a new item in hazarddetails with the masterid of an already existing item in hazardmaster.

MasterGallery.Selected.ID=number

masterID column in sharepoint = number

The form will create a new record but it will not write to all columns. MasterID and another column with type Text will not write.

I've tried everything i can think of, have spent hours upon hours trying to solve this problem 😞

 

the masterId column is called masterId, not title (i checked)

the column format and the form input control are the same matching types of data (i checked)

 

can anybody help?

1 ACCEPTED SOLUTION

Accepted Solutions
ChadVKealey
Memorable Member
Memorable Member

@sb92 , to clarify the sequence, you have a gallery showing the "HazardMaster" list. You click something to open a form allowing users to create a new "HazardDetail" that will be linked to that Master item. You say you have that Patch statement in the "OnSuccess" for that form, but that is what happens when the form is submitted. So, the form submit is creating an item, then the Patch statement would create another item (since you're using "Defaults(datasource)") in the Details list. Is it possible that this is what's happening (two Detail items are being created) and you're looking at the one generated by the SubmitForm action, not the Patch? 

What you might want to do, rather than using the Patch, is adding the "MasterID" field to the form and set it's Update property to "MasterGallery.Selected.ID". You can then hide that field on the form (NOTE: set visible to 'false' - do NOT delete/remove the field!). I would actually leave it visible for testing; once you're sure it's entering the value correctly, hide it.

View solution in original post

15 REPLIES 15
RandyHayes
Super User
Super User

@sb92 

Can you provide some of the formula that you are having problems with?

In general, you will reference the yourForm.LastSubmitted.ID to get the ID you are looking for in your formula.

i.e. (guessing here because not sure what you're actually doing in your formula)

    Patch(yourOtherList, Defaults(yourOtherList), {masterID: yourForm.LastSubmitted.ID})

 

I hope this is helpful for you and gives you a clue - if not, please clarify some of your formula used.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Hi Randy

In my app I only refer to lastsubmittedid when I'm creating two items to two different lists at once on the same screen (a form and a gallery/collection submitted together). This already works fine..

But!

When I already have an existing item in list 1 that already has an ID, and I want to create a related item in list 2 (with a column called masterID which is the same number as ID in list 1) then there is no last submitted form to refer to, as the original item could have been made weeks ago. So what I've done in this instance is set masterid to equals mastergallery.selected.id so that an item created for list 2 can have the same ID as an item in list 1.

Here's the onsuccess formula for the form that creates a new item in list 2 after already selecting an item in list 1 from a gallery on the previous screen:

 

 




 

Patch(HazardDetails,Defaults(HazardDetails), {Title:DataCardValue1_1.Text, MasterID:MasterGallery.Selected.ID, How:DataCardValue2_1.Text, Where:DataCardValue3_1.Text, WhoIsAtRisk:DataCardValue5_1.Text, 'Current Safety Measures':DataCardValue6_1.Text, Probability:ProbabilityEditorDropdown_1.Selected.Value, Severity:Dropdown2_1.Selected.Value, RiskLevel:TextInput1_1.Text, 'Additional Safety Measures':DataCardValue10_1.Text, NewRiskLevel:DataCardValue11_1.Selected, AdequatelyControlled:DataCardValue12_1.Text, 'Senior or Director Sign Off':DataCardValue13_1.Text} ); Navigate(HomeScreen);

ChadVKealey
Memorable Member
Memorable Member

Try wrapping the ID from the MasterGallery in "Value", like this:

 

MasterID: Value(MasterGallery.Selected.ID)

 

You wouldn't think that would be necessary, but I've seen a LOT of cases where it was.

RandyHayes
Super User
Super User

@sb92 

I believe I am putting the pieces together.

But I have some confusion that I need some clarity for - your EditForm is for HazardMaster or HazardDetails?

 

I'm going to assume for this moment that the EditForm is for HazardMaster and that your OnSuccess formula is to create a new record in the HazardDetails with the values from the EditForm (and other places) to populate the columns.

 

If this is all good...read on...if not, stop and clarify.

 

So, the fact that the master record was created prior does not impact LastSubmit.  It will still have all of the values of the record.

 

So, you should change your OnSuccess action formula to the following:

Patch(
    HazardDetails,
    Defaults(HazardDetails), 
    {Title: DataCardValue1_1.Text,                //change this to the column
     MasterID: yourEditForm.LastSubmit.ID, 
     How: DataCardValue2_1.Text,                  //change this to the column
     Where: DataCardValue3_1.Text,                //change this to the column  
     WhoIsAtRisk: DataCardValue5_1.Text,          //change this to the column 
     'Current Safety Measures': DataCardValue6_1.Text, //change this to the column
     Probability: ProbabilityEditorDropdown_1.Selected.Value,
     Severity: Dropdown2_1.Selected.Value,       
     RiskLevel: TextInput1_1.Text, 
     'Additional Safety Measures': DataCardValue10_1.Text, //change this to the column
     NewRiskLevel: DataCardValue11_1.Selected,    //change this to the column
     AdequatelyControlled: DataCardValue12_1.Text, //change this to the column 
     'Senior or Director Sign Off': DataCardValue13_1.Text  //change this to the column
    } 
); 

Navigate(HomeScreen);

NOTE: I have indicated above the "//change this to the column" remarks.  DO not rely on the values of controls in the EditForm during your OnSucess.  They will have changed in many cases (like your form is in New mode, and others).  Instead you should reference the value from the record in the LastSubmit.

So, for example, let's say Title...you should replace DataCardValue1_1.Text with yourEditForm.LastSubmit.Title

Do this same thing with ALL of the columns in your Patch that reference a control in your form and replace with the LastSubmit.columnName

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Hi Chad

I tried that originally and that didn't work either! 

MasterGallery.Selected.ID is evaluating as a number, and it is 29 or 31 depending on which list1 item i have picked so it is defo working in that sense! 

Hi Randy

Sorry no the editform is for HazardDetails. The form is to create a new record in HazardDetails that will be able to be associated to an item that already exists in HazardMaster because the ID of the hazard master is to match the masterID of HazardDetails and vice versa. A HazardDetail item might be created days or weeks after a HazardMaster item has been created.

RandyHayes
Super User
Super User

@sb92 

Okay.  So the point about the LastSubmit column values is highly important to do.  In general the controls in a form should only be referenced in certain situations.  An EditForm has two record properties that supply anything you need from the form - Updates and LastSubmit.  Updates will be all the update properties of the form combined into a record and LastSubmit will be all of the column values that were last submitted (as of the SubmitForm action).

You should not get to rely on the DataCardValuex controls as they can change and give unexpected results depending on your form.

 

Now...going back to the MasterID.  I have a suspicion that your Gallery is getting changed (the selected row) when you are submitting the Form.  This can be because your datasource is being updated (which it is) and your gallery is based on that and it need to re-calculate its rows (very common).

 

So, I would suggest "grabbing" the MasterID in a snapshot variable.  In the action where you do your SubmitForm, add the following BEFORE your SubmitForm - UpdateContext({lclMasterID: MasterGallery.Selected.ID})

 

Then change your formula to the following:

Patch(
    HazardDetails,
    Defaults(HazardDetails), 
    {Title: DataCardValue1_1.Text,                //change this to the column
     MasterID: lclMasterID, 
     How: DataCardValue2_1.Text,                  //change this to the column
     Where: DataCardValue3_1.Text,                //change this to the column  
     WhoIsAtRisk: DataCardValue5_1.Text,          //change this to the column 
     'Current Safety Measures': DataCardValue6_1.Text, //change this to the column
     Probability: ProbabilityEditorDropdown_1.Selected.Value,
     Severity: Dropdown2_1.Selected.Value,       
     RiskLevel: TextInput1_1.Text, 
     'Additional Safety Measures': DataCardValue10_1.Text, //change this to the column
     NewRiskLevel: DataCardValue11_1.Selected,    //change this to the column
     AdequatelyControlled: DataCardValue12_1.Text, //change this to the column 
     'Senior or Director Sign Off': DataCardValue13_1.Text  //change this to the column
    } 
); 

Navigate(HomeScreen);

 

Again...changing those other references to DataCardValues to be the LastSubmit.column

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
ChadVKealey
Memorable Member
Memorable Member

@sb92 , to clarify the sequence, you have a gallery showing the "HazardMaster" list. You click something to open a form allowing users to create a new "HazardDetail" that will be linked to that Master item. You say you have that Patch statement in the "OnSuccess" for that form, but that is what happens when the form is submitted. So, the form submit is creating an item, then the Patch statement would create another item (since you're using "Defaults(datasource)") in the Details list. Is it possible that this is what's happening (two Detail items are being created) and you're looking at the one generated by the SubmitForm action, not the Patch? 

What you might want to do, rather than using the Patch, is adding the "MasterID" field to the form and set it's Update property to "MasterGallery.Selected.ID". You can then hide that field on the form (NOTE: set visible to 'false' - do NOT delete/remove the field!). I would actually leave it visible for testing; once you're sure it's entering the value correctly, hide it.

Hi Chad, what would I write in place of the Patch in the OnSuccess property of the form?

Helpful resources

Announcements

Win free tickets to the Power Platform Conference | Summer of Solutions

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 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**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Copilot Cookbook Challenge | Week 1 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders     Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Top Solution Authors
Top Kudoed Authors
Users online (2,586)