Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Which field cannot be universally required in salesforce? a)Look Up b)Text c)Email 4)Number I refer some guide it is given Answer a)Lookup but when i tried to make lookup field required ,its working. Please Help me out in this.

Thanks in Advance!

share|improve this question
When posting questions such as this, which obviously come from a test or exam, can you provide details of where it came from? That way we can be sure you aren't sharing questions from real Salesforce certification exams and breaching the test taker agreement. – Bob Buzzard Jan 2 '13 at 10:39
up vote 1 down vote accepted

You can make lookup fields universally required in the initial field setup. the documentation is generally very good but sometimes it's not perfect. usually the reason it is not perfect is that sales force makes something possible but doesn't update every single existing piece of documentation with the latest update or upgrade.

I think at the time of its writing you could not do this, but now you can do.

share|improve this answer

Lookup can be made mandatory now .This was recently launched in API 25.0 version so none of the answers are correct.

In API version 25.0 salesforce made lot of changes to Master Detail and also for lookup relationship.

Above is summer 12 release notes .Please go through the same .


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.