Unanswered

Editing record in SP submits new record

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

@RandyHayes Yesterday you were kind enough to assist me in getting my OnSave corrected to show an error for Duplicates on the App ID. It's working great. However, I believe I inadvertently broke the ability to edit a record and save without it creating a whole new record. I'm wondering if the OnSave for SharePoint Integration should have something for the If Edit, do this...If New, do this? Or any ideas how I can fix it? Here's what you gave me for reference:

Categories:

Building Power Apps

All responses (40)

Answers (0)

Sort by

RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@Anonymous

That should not be the case. You are using SubmitForm to submit your record. If your form is in Edit mode and has a valid record, it will update that record when submitted. If the form is in New mode, then the internal record is empty and it will create a record on submit. Also, if the form is in Edit mode and the record provided in the Items property is a blank record, then it will also create a new record.

So, if you are editing a record - are you seeing all the details and information in the form that is relevant to that record?

If in doubt on things, please provide:

- The OnSave action formula of the SPI (SharePointIntegration object)

- The OnEdit action formula of the SPI

- The Item property of the form.

Also, which mentioning things...where is the formula that you provided in this post (that we worked on yesterday) being used?
Drrickryp Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
@Anonymous ,

Try

If( IsBlank( Lookup('Test Automation Governance Report Checklist', 'App ID'=DataCardValue2.Selected.Value ) ), SubmitForm(SharePointForm1), Notify(...) )
RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
@Drrickryp

The formula currently is correct:

If( Lookup('Test Automation Governance Report Checklist', 'App ID'=DataCardValue2.Selected.Value, true), SubmitForm(SharePointForm1), Notify(...) )

Doing an IsBlank on a lookup is not needed. If you are testing if a record exists or not, it is important to realize that the third parameter of the LookUp function is what you want to return from the LookUp (normally a column name or a formula of column names, or a calculation). So, in the above, we want LookUp to return true when the record is found. Otherwise it will return false.

However @Anonymous problem is with the form now, not with that function.
Drrickryp Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@RandyHayes

OK, I get it but in the screenshot, it shows a "!" in front of the lookup. That seemed weird to me and affected the logic.
RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@Drrickryp

Yes - that "nots" the true...So in the formula if there is NOT a true record result, then submit, else notify.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Yes, when I click on the record, the details are correct. When I hit Edit in sharepoint on the record, the details are accurate still.

- The OnSave action formula of the SPI (SharePointIntegration object) - This is the screen shot i provided above.
- The OnEdit action formula of the SPI - EditForm(SharePointForm1)
- The Item property of the form - If(IsBlank(SharePointIntegration.Selected) || IsEmpty(SharePointIntegration.Selected),First([@'Johanna Test List']),SharePointIntegration.Selected)
RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@Anonymous

Okay...all of the formulas look good!

So, to clarify - you are stating that if you click on a record to edit it, it shows up fine in the form, yet when you click the Save button, it creates a new record in the list and does not update the existing edited record?
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Correct...To add more clarity, its not submitting a new form because the dup check we put in yesterday is seeing it as a "new record" and wont allow it since that App ID already exists.
RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
@Anonymous

Okay...I'm reading between the lines a little here, but the issue is that you're not able to submit the form because, since it is edit, then the record already exists - which makes sense.

So, let's alter that formula then to:

With( LookUp(Test Automation Governance Report Checklist, 'App ID'.Value = DataCardValue2.Selected.Value ), If(SharePointIntegration.Selected.ID = ID || IsBlank(ID), SubmitForm(SharePointForm1), Notify("App ID Already Has a Row. Please Find and Update Existing Row") ) )
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Tried that, still getting our notify message that App ID already has a row.