Strangeness with custom fields

[stevec]

Hi,

I have developed custom fields to the opportunities module - 'territory' and 'product type'. They are custom drop downs (mandatory) and also used in the advanced search.

I added the fields in the middle of the upgrade process to 4.2 from 4.01. The short of it is - the process went like this:

copied live system (4.01) to test machine
upgraded test machine to 4.2
added fields to live version (4.01) and to test machine (4.2) - all mods were identical - names, places etc.
upgraded live system


Now, they are behaving differently.

The test machine that had the fields added after the upgrade works as expected - searches work and it complains if they are left empty (mandatory)

First, the live machine didn't show the contents of these fields. This was fixed by going to the custom field page and re-saving each one (not changing anything)

However, now (though I'm not sure if it has ever after the upgrade), you can save an opportunity without selecting anything from the drop downs - they are no longer mandatory - though any changes are saved.

Also, you cannot search on these fields. If you try, the search criteria used do not include those values selected and they are reset in the search box when the page reloads.



I've confirmed that the php and html pages are identical on both machines - so it must be something to do with the database contents. But I'm not sure where to look as I thought that all the symptoms point to problems with vardefs etc.

And to clarify, the opportunities_cstm have the same structure across the two machines - and I've rebuilt the extensions, relationships and upgraded custom labels.

Thanks

[stevec]

ignore that - my fault - used a lower case character whereas the other had upper case.