Edit line item in SharePoint list

[kilaj1]

I have a single SharePoint list that had about 20 columns. I've customized the form directly from the list library.  I have 5 pages, 3 are based on what is selected on the home page. 

What I'm trying to do is after the initial entry I want users to be able to go back in and enter final notes, which is done in 3 columns, "Notes" "Done by" (people picker) and "Date done by".  I have these columns showing on another page which is only accessible once you go to edit an existing record (by line item's ID)

I've tried using Patch but it creates a new line entry in SPO list, i think the problem is that the form on this page is not connected to the list library via ID.  I've tried quite a few things including changing the Item setting and using lookups.  should i be using a gallery?

[RandyHayes]

@kilaj1 

If you are using an EditForm, then you should be doing a SubmitForm on your form, not a patch.  SubmitForm will take care of new and existing automatically based on its mode and Item properties.

I hope this is helpful for you.

[eka24]

Kindly watch this tutorial from @RezaDorrani 

https://youtu.be/9gI9OscTLD0?t=14 

It is on multi forms. From your description, it would help achieve it

------------

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

[RandyHayes · Accepted solution]

@kilaj1 

Or watch this video on splitting forms properly - Reza's video breaks the functionality of a form...sorry to say.  Using Patch on a form reduces all the built-in functionality to nothing.

[kilaj1]

Thanks!, those video change everything I've been doing so far with PowerApps and EditForms. I like the video @RandyHayes mentioned seems a bit more to what I want to do.

The patching did work with another PowerApp I created, but it defiantly needs a revamp now that I see this way.

[RandyHayes]

@kilaj1 

Yes, in my video I am highlighting how to maintain functionality of the form. Things like - Valid, Unsaved, OnSuccess, OnFailure, LastSubmit, etc. all work with the method I show there.  When you use Patch to submit forms, you lose all of that functionality.  Yes, you can "make it yourself" with the Patches, but why bother when the feature is there? just use it.  The less you have to "build", the less you have to troubleshoot and maintain.

[kilaj1]

I seem to be running into an issue where information isn't cascading down to the master form, some is others not.

[RandyHayes]

@kilaj1 

What is the Item property of your Master form?

[kilaj1]

Its:

Patch(glbCurrentRecord, RecordUpdateFrom.Updates,MarkasForm.Updates,MergeForm.Updates)

[RandyHayes]

@kilaj1 

Can you isolate which form is not providing its values properly?  For example, let's say that RecordUpdateForm is not showing some values in your master form, then look at any particular column in the form that is not working and see if there is something wrong in the Update property of the datacard for the form.

OR...in other words, have you changed any Update properties on any forms?