We are testing the new 2024.1.10 in Pilot Cloud/MT and none of our UD fields are binding. We get an error on any screen that has a custom field on it.
Is anyone else seeing this?
1 Like
I would definitely submit a case. I’m not seeing that issue and I’m sure others on here would be screaming if that was happening across the board.
I have a case open. Hoping others were seeing it also (so it’s their issue not ours)
1 Like
Could be something simple… especially if it is effecting ALL of your forms with UD fields. Sounds like something got botched or skipped in your update, like they need to regen your data model or something. Here’s hoping!
Unfortunately this sounds like what has happened to several users, not just MT.
Seems like the db regen was skipped or failed.
We cannot even log into our Pilot environment today since they completed the 2024.1.10 updates. When launching Pilot it seems to install an old update as the Menu Style selection is available on the log in menu and then we get an error. Tried downloading a new install file and got a different error. I have a case open for our issue.
We are finally in our Pilot environment after the 2024.1.10 upgrade. Thought I would update this post with what our issues were in case it helps others.
-
Our Sysconfig file had to be updated by the Cloud Ops Team to reflect the current version 2024.1.10. Prior to this it was attempting to update our environment with the 2023.2.11 version even though we were at 2023.1.8 before the 8/13-14 upgrade.
-
Once we were able to log into Pilot and had the correct version - we received the “invalid binding” error on Classic menus that had UD fields which required Cloud team to run a Data Model regen and App Pool recycle.
1 Like
Same Here - put in a ticket to Regen the Data Model.
They responded in a few hours.
All is good now.
DaveO