We upgraded from 10.1 to 10.2, and afterwards one of my customizations is causing an issue.
All the customization does is add a few UD fields to the form, zero code done. However, when launching the form with that customization it makes all of the fields read only.
Anyone run into this before? I’ve gone to customization maintenance and validated it.
Nope, never come across this before (and have done a lot of 10.1=>10.2 upgrades). When you say all fields are disabled, does this include key fields ? If you can post the customisation here I can take a peek / check if it happens here. If key fields are still enabled then my bet would be the form’s read-only field may be set, I can think of two ways of doing this
Deliberately in script code (and you’ve mentioned there isnt any code), and
The read-only flag is brought through from the corresponding checkbox on the menu maintenance screen so double check its not somehow become ticked.
If however key fields are disabled as well then I’m stumped but willing to see if can replicate.
If you run the screen without the customizaton does it work normally?
have you tried to save the customization as another name and then run the new one?
Well I’m glad it’s Friday. That’s exactly it, Read Only was checked. No idea how that happened. I’ve never used that checkbox before, didn’t even realize it was there.