App Corrupted After Trying to Change Primary Key Field on A Form

[Anonymous]

I have a SQL Server Backend and I had my PowerApps app working fine until I tried to change a field on my form linked to the primary key of my data source.  After I did that, I received a message "The specified record was not found. Server Response: Resource not found".  I read on the forum that  changing the primary key on a record after it has been created is not supported.  That disappointing.  What's worse is that after I close and restarte the App, I continually get the same error message.  I deleted all the data from all of my tables in my SQL Server Database and I still get the same error mesage.  I even tried to drop and recreate the table that I thought was impacted and it still doesn't resolve the issue.  I also tried recovering from an earlier version of my app and it still didn't work.   It's as if trying to change the primary key on a form corrupted my application or my database or both.  I'm basically dead in the water.  This happened to me 2 days ago as well on a different screen in my app.  I recreated the form from scratch and that was the only way I could get things working again.  This points to the app somehow being corrupted, but recovering from an earlier version of the app didn't solve the problem this time so I am stumped.

I should point out that I have foreign key relationships/dependencies set up in my sql server database which was doing a nice job maintaining referential integrity in my App.

Has anyone run into these issue and do you have a resolution.

Thanks,
Jeff

[v-micsh-msft]

Hi @Anonymous,

I think this reason here should be PowerApps is using the Primary Key to identify the row in SQL Table, so changing the Primary key value within PowerApps may not work, as PowerApps can't identify the proper row.

For a workaround, please consider to have the Primary key set to auto_increment, which is handled by the data source side, so that it can't be changed (but readable) under PowerApps.

Regards,

Michael

[Anonymous]

Michael,

Thanks for your reply.  I understand that Powerapps doesn't support changing the value of a primary key.  The bigger problem is that when I did change the value of the primary key by mistake, it corrupted the screen of my application.  I tried everyting to recover the screen.  I logged out and logged back in. Restarted Powerapps.  I deleted all the rows from all of my tables in the database. I even tried to recover an older version of the applicaton from before the key was changed.  Nothing worked.  The application and all of its older versions of that screen were corrupted.   When this happened earlier to me, I had to recreate the screen from scratch.  The second time this happened to me, I worked for hours and finally figured out that if I delete the primary key fields from the screen/form and re-add them, the problem/corruption is fixed.  I want to use regular fields as key fields as it makes more sense in setting up the relationship rules on the backend.  I was simply going to make those fields view only on my powerapps screens,  which highlights a second major issue with Powerapps.  I was testing the displaymode.view  on one of those primary key fields.  It looked like a view only field because it took the border away but it allowed me to changed the value of the field and save it.  I thought diplaymode.view would give you a view only view of a field and not let you change it.  that was not the case.  When you combine that issue with the other issue, you have a giant Powerapps headache.

[Anonymous]

I just received an automated email asking if I received the answer I needed. No, the issue is not solved

[bdc604]

I feel your pain. 4 days customizing a multiscreen form for SP, no way to dl/export. It buggered right up, even after trying to remove all code and restoring prev versions. Combo box lists were flying off to weird places, flashes way beyond post backs, datacard values getting rejected when referenced. fml.

[bdc604]

the real fun part is going back, documenting and screen shotting ALL the settings and functions, because you can’t keep it as reference, your only option is to delete it. Its associated to a live list whose data and relations are way more important than the form. Atleast there is a 50/50 chance it might be stable next time around... maybe...