New bug with dependency field in opportunity module
we have some custom dependency fields that gives us choices that are not suppose to be there in the opportunity module
i will try to explain this
We have a few dependent fields that only have one choice if the parent field is chosen then that dependent field will default to that only choice but for some reason since last week the -None- choice started defaulting even though the -None- is not chosen as a valid choice for that parent field. but that bug is only there if the parent field was already there prior pressing the modify button. because that field was converted from a reference. all other Parent/child field work like it used too, except for the parent/child match that was present on opening the page.
How can I correct this to have working like it used too.