It’s transparent so I don’t know how many times it has happened but we are definitely having to run the data fix to remove corrupt personalizations less frequently now.
3 Likes
Depending on the version you downloaded, the parent layer support may have gotten lost. I’ve updated this and tested it on 2024.1 as well.
Main post with most recent updates: Need votes for a program to remove kinetic personalizations - #17 by hmwillett
5 Likes
The updated 2023.1 file worked - thank you!
1 Like
As @aosemwengie1 said in October, version 2024.1 is supposed to fix this.
Well, I’m still on 2023.2, (waiting for 2024.2 to mature a little more) and I’m still purging corrupt personalizations by hand.
I tell that story to tell this story:
I assumed that the app name in the URL (highlighted below) was the name of the thing.
So I looked for Ice.UIDbd.SNLotTrack and there were no personalizations against it.
Turns out the personalization was stored against Ice.UIDbd.Template. So I deleted that, and my screen worked again.
Glad there is a last-update column to sort on!
2 Likes
Eerie…we’re 2023.2 as well…and considering a jump to 2024.2 at some point. Out of the blue, someone had trouble with Case (HelpDesk) Entry today. Got a datafix, nuked both ERP.HelpDeskEntry and App.HelpDeskEntry personalization records…and got it back working again.
(Insert “case of the Mondays” reference here.)
Case of the Tuesdays too. Another user had her Sales Order Entry personalizations go FUBAR this morning. Glad that generic datafix hadn’t expired yet.