Household field originally "required", then "un-required" still behaves as required

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a new custom field on a Household object and check "required" box
2. Create a new Household - note red bar on newly custom created field
3. Edit the new field definition to un-check the "required"  checkbox
4. Save the field definition
5. Re-open field definition to verify "required" is unchecked
6. Create a new Household and note custom field still has red bar and behaves 
as "required"

What is the expected output? 
Expect field to not have red bar and not prevent saving of Household if blank

What do you see instead?
Field behaves as "required" field

What version of the packages are you using?
Contacts & Orgs ver 2.0
Households ver 2.0.8

Please provide any additional information below.
Tried to update to Contacts & Orgs 2.0.2 but it failed due to so-called 
required field ifp_Contact_Dear__c

That field has initially "required", then I unchecked the box, but it continues 
to behave as required.

Excerpt from installation failure email follows:

Problem:

1. Apex Classes(01pA0000002Z42W) 
test_leadconvertoverride.newLeadConversion_Test();
test_leadconvertoverride.newLeadConversionMerge_Test()
System.AssertException: Assertion Failed: Expected: 1, Actual: 0
(npe01)
External entry point;
System.DmlException: Insert failed. First exception on row 0; first error: 
REQUIRED_FIELD_MISSING, Required fields are missing: [ifp_Contact_Dear__c]: 
[ifp_Contact_Dear__c]
(npe01)
External entry point

2. Apex Classes(01pA0000002Z42V) test_accountviewoverride.accountViewOverride()
System.DmlException: Insert failed. First exception on row 0; first error: 
REQUIRED_FIELD_MISSING, Required fields are missing: [ifp_Contact_Dear__c]: 
[ifp_Contact_Dear__c]
(npe01)
External entry point

3. Apex Classes(01pA0000002Z42Q) test_contactmergecontroller.exerciseUI();
test_contactmergecontroller.failMergeWithDeletedRecordSelected();
test_contactmergecontroller.failNextStepWithDeletedRecordSelected();
test_contactmergecontroller.merge1Org1OneToOne();
test_contactmergecontroller.merge2Individuals();
test_contactmergecontroller.merge2OneToOne();
test_contactmergecontroller.merge2OneToOneInSameAccount();
test_contactmergecontroller.merge2OneToOneOpps();
test_contactmergecontroller.merge2Organizations();
test_contactmergecontroller.merge2PrivateContacts();
test_contactmergecontroller.merge3OneToOne();
test_contactmergecontroller.tooFewContactsSelected();
test_contactmergecontroller.tooManyContactsSelected()
System.DmlException: Insert failed. First exception on row 0; first error: 
REQUIRED_FIELD_MISSING, Required fields are missing: [ifp_Contact_Dear__c]: 
[ifp_Contact_Dear__c]
(npe01)
External entry point;
System.DmlException: Insert failed. First exception on row 0; first error: 
REQUIRED_FIELD_MISSING, Required fields are missing: [ifp_Contact_Dear__c]: 
[ifp_Contact_Dear__c]
(npe01)
External entry point;
System.DmlException: Insert failed. First exception on row 0; first error: 
REQUIRED_FIELD_MISSING, Required fields are missing: [ifp_Contact_Dear__c]: 
[ifp_Contact_Dear__c]
(npe01)

Original issue reported on code.google.com by John.Sa...@gmail.com on 7 Jun 2011 at 8:35

[GoogleCodeExporter]

Hi John-

Just walked through the steps to reproduce and I wasn't seeing the same thing 
you were. Can you email me your org ID and grant login access so I can take a 
look? I can be reached at kbromer at the domain you'd expect.

Thanks-
Kevin

Original comment by kbro...@gmail.com on 7 Jun 2011 at 8:47

[GoogleCodeExporter]

Kevin,

Thanks for looking at this so quickly.

Org ID was emailed and login access granted. 

Also - I should have mentioned that I discovered this while researching why 
Households were not being created automatically when a new contact is created, 
which led me to issues 121 and 249

Best regards,
-John

Original comment by John.Sa...@gmail.com on 8 Jun 2011 at 3:10

[GoogleCodeExporter]

Hey John-  

The ifp_Contact_Dear__c field is on the Contact object - It looks like the 
field level security is set to required on the page layout. There are two spots 
you can set 'requiredness'. The actual field, which makes it required for all 
users, or the layout, which would be based on layout assignment. Best way to 
check a field is to click on the label when viewing it in the setup menu, and 
hit 'View Field Accessibility'. The system will tell you if it's required and 
what's causing the requiredness. 

I'm going to go ahead and close this issue, but let me know if anything else 
crops up.

Hope that helps!
Kevin

Original comment by kbro...@gmail.com on 8 Jun 2011 at 4:45

• Changed state: Invalid

[GoogleCodeExporter]

Hi Kevin,

My error - you are correct that the field was indeed required on the page 
layout. My apologies.

-John

Original comment by John.Sa...@gmail.com on 10 Jun 2011 at 1:53