We have several different types of company relationships we capture in CRM that all fall under the umbrella of the 'Account' entity. For example our customers, of course, are captured as 'Account'...but also Banks, CPA's, etc...any company we have
a working business relationship or partnership with. We added an 'Account Type' field driven by an optionset which is how we distinguish between account types.
What I'm running into, on the various forms we created for our CRM users, we will have a lookup to link a customer account to say, a bank or a CPA that they use. The problem I run into, is that when a user creates a new entity (such as an opportunity
or other custom entities that would link to a different type of account), all these lookup fields prefill with the "customer" account information when the reality is we want this blank and encourage the users to have to select either a Bank or a
CPA, etc (the lookup fields are configured to use a specific view...we have views created to only display specific account types that are intended to drive these lookup fields).
This is how we were advised to handle these Account to Account relationships by our Microsoft Certified Partner when we implemented Dynamics CRM. I'm thinking in hindsight it may have been wiser to create these different 'accounts' as custom entities.
For now this is what I'm stuck with though...so any ideas how to prevent these lookup fields from prefilling? Thanks!
