The specified record was not found. Server Response: <Sharepoint List Name> failed: Resource not found

[csheets]

Took about 6-8 months building a new complex form for our New/Existing/Separated employee request form in our company and extensively tested it.  Users were able to submit forms just fine, and are still able to submit forms just fine during testing and I tested the form with a group of about 15-20 users.

After throwing the form into production, we have had a number of random users say that they cannot see anything in views I created for them nor can they submit new forms.  These users get the error stated in the title of this post flashing atop their browser:

The specified record was not found. Server Response: <Sharepoint List Name> failed: Resource not found

This cuts ties to pretty much every connector being used in the form rendering everything completely useless in the form itself.  Its almost 50-50 now with users that get this and users that don't.  There is nothing tying all the user that get this together, as everyone in our organization has full control and/or edit access to every list tied to this form.

Can anyone help PLEASE?!?!?!

Just to clarify:

I can log into a user account that has these issues on my PC and I get the same error.  I can then log into the powerapp as a user unaffected by the issue on my PC, and its just fine.  Its a problem specifically with the user account and permissions I am guessing.  Would wiping all permissions and resharing the application do anything?  I also ran the script for it NEVER to ask users permissions to login, fearing that these affected users clicked "Dont Allow" originally.  Script ran without a hitch and affected users are still affected and normal users can get in without any issues.

Edit

I "Saved As" my huge application, gave permissions to everyone, and logged in as the problem user.  When prompted to allow connections, I allowed them.  User had ZERO issues accessing the information.  My guess is that the users who are having problems in my organization clicked "Do Not Allow" when entering the application for the first time, hence forever breaking that connection.

Can I restore that connection via unsharing the entire app and resharing, or will that not re-prompt the users?

[csheets · Accepted solution]

I used the "Save As" function on the form, made a new one, ran the powershell script to suppress the connection question (found here https://www.anupams.net/suppress-user-consent-popup-in-powerapps/), and then changed all the shortcuts to point to the new form.

[FCGALLEG]

Hi Csheets, 

Thanks for share the info.

Javier

[Abhay08]

@csheets I am facing same issue Can you please explain me the solution. Help will be much appreciated.

[csheets]

@Abhay08 Basically the application became corrupt in SOME way.  Saving As and then going to where I had the shortcuts on the intranet pointing to the corrupt version and changing them to the new version fixed my issue.  Also for every new app I build, I run the command in the link in the solution so that users never have to agree or connect to anything via a dialogue popup in the app when its first accessed.

This solved the issue for me at the time and I have not run into it again.  That being said, it may not solve the issue for you, as I am not sure how bad your situation may be.  Hope it helps though!

[Abhay08]

@csheets  

I have a canvas app connected to SharePoint list all users are able to submit the form but one user is facing issue on submitting the form: The specified record was not found. Server Response: <Sharepoint List Name> failed: Resource not found 

 
I checked the list permissions of that user and it is matching with other users.  When I made that user to submit the form through a copy of the original application which I created using “Save as” option in original application then it’s working fine with that user. 

I am not sure what I am missing, Any help would be really appreciated

[csheets]

@Abhay08Yeah, my issue had nothing to do with permissions either, so I threw that out the window.  Sounds like the user having the issue DOES NOT have the issue when using the app you had Saved As from the original, so that just means that for some reason your original current application is just busted/corrupt/broken for that user.  I don't TECHNICALLY know why that is, but it happened to me as well.  That's why I don't use the "broken" application anymore.  I saved it as a different name and started using the new one for everyone without any issues.  That is exactly what I would recommend in this case if it's not too much of a hassle.

Again, I don't know the technical reasons behind the problem or the fix, I just know it works for me and it sounded like it may have worked for you in that instance with the user experiencing issues.

1. Go into the current app that is "broken" for the user
2. Save As a different name
3. Test the new Saved As version of the form with users who had the issues
4. If it works, deploy the new version of the form wherever you had links to the old one

If this doesn't work, I apologize.  I am not as technical as most on these forums, but again, this did help in my situation when no other answer was available or would suffice 🙂

[Abhay08]

@csheets Thanks for the response I appreciate your help.
Just want to know if I create new application from original/broken app then I have to reshare new app with all users and update all the users about new app with new link ???? 
If so, ? Is there any way I implement the new app and all the existing users won’t know about the changes ? 

Since there are lot of users If existing service is interrupted for them and I need to update all of them then It would be difficult to achieve. 

[csheets]

@Abhay08  I had a link in an email that went out to users when a form was submitted and/or needed approved.  That link in those older emails still made them use the old form, which I supported for about 3 months or so after creating the new one.  That old app that works for all but 1 now will continue to work for all but 1.  I immediately changed my Power Automate to send out the new links to the new form.  I also had a link on our Intranet site that I replaced with the new link, so if users went that way they would be into the new form.  No one ever knew the difference once the old form/app was phased out 🙂

If users bookmarked the old form you MAY have a problem.  Then you would just send out mass email communication briefly explaining what happened and why old links will continue to work until they don't basically.

Note:  I also version my applications that I create.  I just create a label either in the title bar or footer of my app on the front page that says "<username> is logged into version - LIVE 4.6" or "<username> is logged into version - OLD FORM 1.5" or what not and I manually change the version number when I work on the form, going up .1 when its something minor and 1 whole point when its a major release.  This especially helps troubleshoot when you have 2 versions of the form out there.

[skeepee]

I have an app that is doing this with a SharePoint list data source. One of the columns in this list throws this error regardless if I reference it with its display name or its original name. It even happens when I add a form to a new screen. That makes zero sense because when a form is added to a screen, Power Apps queries the data source itself to get column names and details. How could a column be "not found" when the data source itself reports that it exists??