I am current engaged in a project where a vendor suggested to the customer to use the same entity for various purposes. That decision might have worked for some organizations, but it did not have a foresight of the future requirements of the organization.
In a recent project, we had a requirement to display cases to the portal that are associated with either Contacts or Accounts. Our case entity had a related entity called Case Contacts, and our account entity had a related entity called Account Contacts. The account entity had a list of all the cases associated with the account.
Recently we had a requirement for one of our Dynamics Portal projects that I thought we could share with the community. The requirement was pretty simple. We had a many to many relationships between Contact and Account (so that a contact could belong to multiple Organizations) that needed to be displayed in a dashboard.
