Why not to make a read-only field required
19
Mar/074
Mar/074
This action can be filed under stupid mistakes.
On opportunities we have some calculated fields which are read-only. Somewhere in the system requirements was said that one of those fields (revenue) should be required for a certain sale stage. Of course this was not a good requirement because you can’t fill in a read-only field.
For some reason, I made the field required (don’t ask why) and the changes where put in the SRF which was launched today in the UAT environment. Of course this was a blocking issue. I never felt more stupid then today.
Comments (4)
Trackbacks (0) ( subscribe to comments on this post )
Leave a comment
No trackbacks yet.
8:01 pm on March 22nd, 2007
Siebel consultants don’t unit test???
9:05 pm on March 22nd, 2007
I should have done a unit test, but it was not ment that al those changes where released on the UAT environment.
9:34 am on March 28th, 2007
SOME Siebel Consultants don’t unit test… They are mostly named Wim.
8:09 am on June 6th, 2007
LFMAO