
I have different "types" of businesses to track, but there are some issues with using the account type.
One way is to create a recordtype on the account for the different types of businesses.
But then the user is faced with always filtering out accounts on a record type, where if it was a custom object, I can keep the Account object clean with one type of business. But will I lose functionality if I use a custom object instead. If so, what are the cons.
2 answers
I'd say the biggest consideration here is reporting. Salesforce doesn't let you do ad-hoc joins of unrelated tables, so I wouldn't recommend a new object for each new type of business. This is a good use case for record types. You could also add in some conditional sharing rules, if you only want some users to see some certain records types.
The biggest con is reporting, and the fact that you can't join unrelated tables like you can in something like crystal reports.
Do you have different sets of users who need access to these different types of businesses? And also, by using Accounts, you can leverage other standard objects like Contacts, where as a Contact related to a custom object suffers from visibility problems. A Contact must be related to an Account in order to be visible to other users besides the contact owner.