Answers.Body: <p>Frankly, CiviCRM core should disable the Home address location for Organizations, and the Work address location for Households.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-16T16:47:34.157Z
Answers.Text: I agree. Enabling these types based on context would probably lead to less data entry mistakes overall. And it can bite you hard when your addresses or phone numbers have inconsistent location types!
Answers.UserDisplayName: LunkRat
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-09T19:56:07.393Z
Answers.LastActivityDate: 2015-06-09T19:56:07.393Z
Answers.UserDisplayName: Joe Murray
Answers.Body: <p>I suspect doing this in jQuery via a custom behavior template addition: </p>
  
  <p><a href="https://civicrm.org/blogs/dave-greenberg/now-its-easier-add-custom-behaviors-templates" rel="nofollow">https://civicrm.org/blogs/dave-greenberg/now-its-easier-add-custom-behaviors-templates</a></p>
  
  <p>is probably a lot lighter weight, than an extension</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-09T07:40:08.537Z
Answers.LastActivityDate: 2015-06-09T07:40:08.537Z
Answers.UserDisplayName: Donald Lobo
Answers.Body: <p>If the solution suggested by Coleman does not work, you will have to create a little extension that removes some of the options based on contact type in a buildForm hook? Or alternatively validates the selected location type against the contact type in a validateForm hook</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-09T07:28:57.657Z
Answers.LastActivityDate: 2015-06-09T07:28:57.657Z
Answers.UserDisplayName: ErikH - CiviCooP
Answers.Body: <p>The cheapest solution would be to combine "Home" and "Main" into one option that can be used for both individuals and organizations. Just have to come up with a word that has both meanings...</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-09T01:42:23.530Z
Answers.Text: Like Physical Location ?
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-13T08:03:40.950Z
Answers.Text: Just using the Main location type seems an option to me.  For an individual their main address is usually their home address
Answers.UserDisplayName: JoAnne
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-16T16:48:38.280Z
Answers.Text: Thanks Coleman for your sensible and practical answer. It ended up being the solution to my issue.
Answers.UserDisplayName: LunkRat
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-08T22:09:28.470Z
Answers.LastActivityDate: 2015-06-08T22:09:28.470Z
Answers.UserDisplayName: Coleman
Body: <p>I would like to disallow certain address location types on Organization contacts—for example I don't want to allow "Home" addresses on an Organization. </p>
  
  <p>I would also like to disallow "Main" address type on the Individual contact  types. </p>
  
  <p>Anybody try this before?</p>
  
Tags: <addresses><contact-types><location-type>
Title: Disable certain address location types depending on Contact type?
ThreadText: # Disable certain address location types depending on Contact type?
  
  (Asked by: username_0 on 2015-06-08)
  
  I would like to disallow certain address location types on Organization contacts—for example I don't want to allow "Home" addresses on an Organization.
  
  I would also like to disallow "Main" address type on the Individual contact types.
  
  Anybody try this before?
  
  **Tags:** addresses, contact-types, location-type
  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_4 on 2015-06-08. Score: 3 | Accepted answer
  
  The cheapest solution would be to combine "Home" and "Main" into one option that can be used for both individuals and organizations. Just have to come up with a word that has both meanings...
  
  > **Comments:**
  > **username_5**: Like Physical Location ?  
  > **username_6**: Just using the Main location type seems an option to me.  For an individual their main address is usually their home address  
  > **username_0**: Thanks username_4 for your sensible and practical answer. It ended up being the solution to my issue.  
  
  ---
  
  ### Answer by username_1 on 2015-06-09. Score: 2
  
  Frankly, CiviCRM core should disable the Home address location for Organizations, and the Work address location for Households.
  
  > **Comments:**
  > **username_0**: I agree. Enabling these types based on context would probably lead to less data entry mistakes overall. And it can bite you hard when your addresses or phone numbers have inconsistent location types!  
  
  ---
  
  ### Answer by username_2 on 2015-06-09. Score: 1
  
  I suspect doing this in jQuery via a custom behavior template addition:
  
  <https://civicrm.org/blogs/dave-greenberg/now-its-easier-add-custom-behaviors-templates>
  
  is probably a lot lighter weight, than an extension
  
  
  ---
  
  ### Answer by username_3 on 2015-06-09. Score: 1
  
  If the solution suggested by username_4 does not work, you will have to create a little extension that removes some of the options based on contact type in a buildForm hook? Or alternatively validates the selected location type against the contact type in a validateForm hook
  
  
  ---
  
  