function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Andrew CoxAndrew Cox 

Missing dependent object: Field: Contact.OtherAddress

Hello,
  • I have a custom VF page with a custom APEX controller behind it.
  • I've tested the page in a Sandbox and then deployed it successfully to production a while ago.
  • It's now failing in production with the following error "The configuration of your org has changed, please reload the page. Missing dependent object: Field: Contact.OtherAddress" - this happens when I click a submit button on the page.
  • I am not using the OtherAddress field in the page or controller as far as I can see.
  • I have tried incrementing the version of the API to 31.0 on both page and controller (having seen a similar discussion (https://developer.salesforce.com/forums?id=906F00000008x7wIAA)).
  • When I did this the failing page worked for one submit - but then went back to failing on next use!
I'd love help. Please! :-)
Best Answer chosen by Andrew Cox
pbattissonpbattisson
Hi Andrew

The OtherAddress field should still be in beta release according to the API documentation (https://www.salesforce.com/us/developer/docs/api/Content/sforce_api_objects_contact.htm). Did you have this field enabled for you to try?

I would recommend contacting support regarding the issue and seeing if they can check whether this is turned on or not as I believe that is the root of the issues. 

It would be worth double checking that any classes, triggers etc called from this controller and page are also at the latest API version.

All Answers

pbattissonpbattisson
Hi Andrew

The OtherAddress field should still be in beta release according to the API documentation (https://www.salesforce.com/us/developer/docs/api/Content/sforce_api_objects_contact.htm). Did you have this field enabled for you to try?

I would recommend contacting support regarding the issue and seeing if they can check whether this is turned on or not as I believe that is the root of the issues. 

It would be worth double checking that any classes, triggers etc called from this controller and page are also at the latest API version.
This was selected as the best answer
Andrew CoxAndrew Cox
Thank you @pbattison for your reply. Will check out what you suggest and contact support too (if I can - I tried before and they seemed to direct me to the developer forum.)
Andrew CoxAndrew Cox
@pbattison - I updated all referenced class/pages to latest API version and it looks like it's working. Thank you.