title: Getting Error 3007 when I add my Entity Model
body: <p>I am getting an error 3007 when I add my entity model to my solution.</p>
  
  <p>I found these links:</p>
  
  <p><a href="http://marko.unite.si/post/2008/11/19/Problem-in-Mapping-Fragments-in-Visual-Studio-2008s-Entity-Model-designer.aspx#comment" rel="nofollow noreferrer">Good explination</a></p>
  
  <p><a href="http://techiethings.blogspot.com/2009/03/entity-framework-error-3007.html" rel="nofollow noreferrer">Short answer</a></p>
  
  <p>About this error:</p>
  
  <blockquote>
    <p>Error 1   Error 3007: Problem in Mapping
    Fragments starting at lines 89, 94:
    Non-Primary-Key column(s) [Person_ID]
    are being mapped in both fragments to
    different conceptual side properties -
    data inconsistency is possible because
    the corresponding conceptual side
    properties can be independently
    modified.</p>
  </blockquote>
  
  <p><strong>Their Answer:</strong> I agree with their conclusion that by simply deleting the Scalar Property Person_ID and leave the Navigation Property my problem is fixed. However this is not very scalable since I am dynamically building my database and my entity is updated very often. I dont want to have to go through and clean up my entity every time I update it.</p>
  
  <p><strong>My Question:</strong> Is there a way to fix the error by correcting the way EF builds the entity? Or is there a way to remove the Scalar Property through code? Perhaps there is even a few options that I am overlooking.</p>