I was wondering if anyone could give me some insight on the way we would like
to use CRM 3.0 from an account perspective. We would like use Accounts for
all accounts in CRM versus using a sub-accounts. Meaning that when parent
account is entered and a so called sub-account they would be on the same
level in CRM. Will we lose any functionality or reporting capabilities if
everything is an account versus having accounts and sub-accounts? We have
made some custom entities that enable us to flatten out our account structure
but still maintain a hierarchy of accounts at the account level and not the
account, sub-account level.

Any thoughts would be appreciated.

Craig,

There's no difference between an account and a sub-account. It's just a
relationship like the parent customer id in a contact or the primary contact
in an account. So you always have a flat view when opening the account view,
unless you change the view criteria to not include accounts that have a
parent account.

--
Michael Höhne, Microsoft Dynamics CRM MVP

Web: http://www.stunnware.com/crm2
Feed: http://www.stunnware.com/crm2/atom.aspx
Custom Lookup Dialog: http://www.stunnware.com/crm2/?area=customLookup

----------------------------------------------------------

"Craig" <Craig@discussions.microsoft.com> schrieb im Newsbeitrag
news:37E296B0-4293-4119-9448-5C2A50CED53C@microsoft.com...

Yup, we essentially have a flat structure in our implementation of CRM. We
just leave the parent account field empty on most of our accounts. (We do
have a few parent child relationships, but for the most part, it's flat).