Got a DNN 4.9.5 instance. A user deleted the user account, and this has orphaned some records. If I could create a new user with the same userid at the database level, that would be helpful.

My thoughts are that the best way to do this would be to create a new user via DNN account management, and then go to the user tables and update the userid to the userid I want. That I think I can do with no problem. users, userportals, userroles, userprofile ... any other tables I need to consider? the aspnet tables join on the username, not the userid, so nothing there, right?

The corollary to this question: I need to ensure that users are not able to delete their accounts. I'm thinking that this will require some customization of baseline DNN. Thoughts on this?

Thanks -

---

pmgerholdt

Am familiar with the changes to soft deletes, and upon reflection realize that you are right, this will fix the problem going forward (upgrading). (Most of my sites are at DNN 6 but a couple sit at 495. Needed to wait for client business cycle to allow an upgrade event).

Regarding the identity insert question for my current situation, though - I don't need to reduplicate every aspect of the original user account. The question remains - If I create a new user, can I then change the userid via database in the tables I mentioned without causing other issues?

All I need is to recreate a user account with a previously used userid. Once I have done that, certain records in a third-party module will no longer be orphaned, and I can then use some in-built features to change the user/owner to a new, active user. That feature will not work with the original user not existing.

Thanks

---

pmgerholdt