OnSuccess not writing masterID column to SPO list

[sb92]

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?

[sb92]

Hi Chad. I removed the patch as you recommended, and added in MasterID to the form, as an editable number. And set its update property to MasterGallery.Selected.ID

And it worked!!!!!!!! Hours tearing my hair out about this and now finally solved. Thankyou so much.

A couple of other columns don't carry across either: RiskLevel and AdequatelyControlled.

They do not rely on the other list at all. They are both text columns on the HazardDetails sharepoint list. On PowerApps, RiskLevel's text property is a nested IF statement and Adequately Controlled is also an IF statement. Any thoughts on why this might be?

The IF statement for RiskLevel is as follows:

If(Dropdown2_1.Selected.Value="Minor",If(ProbabilityEditorDropdown_1.Selected.Value="Frequent","Medium","Low"),If(ProbabilityEditorDropdown_1.Selected.Value="Frequent","High",If(ProbabilityEditorDropdown_1.Selected.Value="Likely",If(Dropdown2_1.Selected.Value="Moderate","Medium","High"),If(Dropdown2_1.Selected.Value="Moderate","Low","Medium"))))

Is it because the IF statement has been put in the DEFAULT property of the text input, when it should be in the UPDATE property of its parent datacard???

Thinking I need to go back and relearn about forms and what their properties mean lol

[RandyHayes]

@ChadVKealey  Good call.  I was switching between a few things here and missed that last post where @sb92 mentioned the form was for what was being patched.

@sb92 Yes...this is a true point that is being made.  There is no need to do a Patch if this is the Detail list.  You just need to put the MasterGallery.Selected.ID in the Update property of the datacard for MasterID

[RandyHayes]

@sb92 

Essentially - Update on a datacard is what is written to the datasource.  Default is what is coming from the datasource.  Your controls on the form manipulate anything in between.

If you're looking for some comprehensive "how to" and "what is" for forms, I would recommend taking a look over my video on the subject.  It will tell you pretty much anything you want to know about forms and a whole lot of things you probably never knew you could do with them.

So in your case above, the Default property of the TextInput control should have your If formula and the Update property should have the name of the TextInput control .Text

[sb92]

thankyou very much. what if the conditions of the IF statement change, will the default value stay up-to-date before the form is submitted? I get confused as some form controls have text properties and others just have default (maybe cos those ones are set to view only, as is the case with RiskLevel)

[RandyHayes]

@sb92 

Well, I was a little concerned on the logic of the If statements and believe that can be simplified and cleaned up a bit, but not overly concerned if it is working for you.  Everything in PowerApps is dynamic.  So as things you reference change, so will they.  This is true for everything except variables - which never change unless you change them.

Get familiar with the control types - especially between Label and TextInput.  Label only has a Text property.  TextInput has a Default property and a Text property.  The Default sets what it is by default (in the context of the form, it is usually the Parent.Default - or the field value)  The Text is what the actual entered text is - it can be either the default (if nothing was altered) or whatever the user enters.

I'd definitely have a look at the video I mentioned. The first part will really tell you much more than I can describe here about forms, properties and controls.

[sb92]

Thankyou both so much for your help, all fields are writing back now, my app now allows for every scenario 🙂 

I just need to create an option now for the user to see a view-only view of the hazard master and all it's details on the one screen. A view-form and a view-gallery should do the trick 😄