I upgraded to CR of 2025.2 and UD columns have a bug that freak out the entire system. DO NOT UPGRADE TO ANYTHING LESS THAN 2025.2.4
Second and I assume this may be environment specific, but when I upgraded to .4 last night from .3 my data model was jacked up and conversion workbench blew up. Before logging in and running conversions, I would recommend doing another data model regen, and recycle of the app server THEN log in just to be safe. I had to re-run conversions and stuff after my data model regen and I’m sure it’s fine but it doesn’t feel good.
When I ran conversion workbench it freaked out because it couldn’t compile most of my BPMs. When I looked at the BPM conversion errors it was a long long list, which tipped me off. Then when I opened my first customization and was baraged with invalid bindings I knew what happened.
Like I said, likely environment specific but couldn’t tell you why. We were using CR as much as we could with the UD column bug on .3 and when I went to .4 my data model was 100% invalid for some reason. Which is crazy because a point release doesn’t run data model regens. so… no idea.
I had the same on a demo environment. Upgraded today from patch 3 to patch 4 to test out the ud field bug in whereclauses.
No bpms on it so didn’t see in conversion workbench. But noticed when testing my rest call that it said the field didn’t exist. So check Ud column maintenance and lo and behold it said out of sync. Regenerated and all was good.
