Accounts in CRM

(0) Share

Report

Posted on by jbuck1285

415

Hello,

Our business has vendor and customer accounts. I need a way to easily distinguish accounts in CRM between these two types.

It has been suggested to me that I use the "Relationship Type" field on the account template, where I can designate whether the account is a customer or a vendor. However, I don't think this is the best solution, as our accounts template includes specific and required fields that would not apply to our vendor accounts.

Is there a way to create different account templates based upon the business relationship? Or, conversely, is there another more efficient route of accomplishing my goal?

I appreciate all insights! Thank you!

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

Vijay Waghmare on at

Like (0)

Report

Since you are having account as either vendor or customer, you can create a "two option set / Boolean" attribute for account form. Based on account type selection (two option) you can hide/show fields or make as business required. This can be easily done using "Business Rules" if you are using CRM 2013 or you need to rely on custom javascript code that will trigger on selection change event of two option set.

And in update mode of account form, disable two option set if there will be no change in account type(vendor or customer).

Thanks,

Vijay Waghmare

Was this reply helpful? Yes No
Suggested answer

Karth on at

Like (0)

Report

Entities such as Account and Contact form the core of the CRM product. The way you want to distinguish Accounts and Vendors depends on your requirement. If your CRM requirements are still evolving, then I would suggest you use the same Account entity and use the Relationship Type field to distinguish between them. In conjuncture to the Relationship Type field, you can configure a form specially to capture the details of the vendor. This form can be completely different from the Account form. You can have CRM display the appropriate form based on the value selected on the Relationship Type field.

Other option, which is less favorite, is to create a custom entity for to store Vendor information. But, if you have a scenario where you need to generate a campaign for the vendors, then this design would fail, as you can only create a list for Accounts, Contacts and Leads in CRM.

Was this reply helpful? Yes No
Alok Singh 910 on at

Like (0)

Report

Hello,

It is good to use the system entity instead of creating new entity. I would suggest to use Relationship type and display the fields based on relationship type value.

If you are using CRM 2013, the same can be achieved through Business Rules (Can Display/Hide/Mandatory/Non Mandatory fields by using Business rules based on relationship type selection) and if using CRM 2011 or other version , require custom Jscript to achieve the same.

Hope this will help you in achieving your requirement.

Alok Singh

Was this reply helpful? Yes No
Suggested answer

Luc @ IT creation D... 1,360 on at

Like (0)

Report

Why dont you just make a new option set with tjust the 2 options and make the Field Business Required?

Was this reply helpful? Yes No
jbuck1285 415 on at

Like (0)

Report

Would it be possible to rename the "Leads" entity and have that be our Vendor Accounts?

Was this reply helpful? Yes No
Suggested answer

Ryan Maclean 3,070 on at

Like (0)

Report

Hi JBuck,

Whilst you could rename the 'leads' entity, realistically the way it operates is quite different to the Account entity, and changing the leads entity may prevent you from adopting the wider functionality of CRM in future.

My recommendation would be to create a Boolean/two option attribute (as has already been mentioned above) on the Account record that allows you to pick whether the Account is a Customer or a Vendor. You could then have additional fields that only become visible if you pick Vendor or Customer. You can then create system views that only display either Customers or Vendors.

You haven't said which version of CRM you are using, but if it is 2013 then this is easily achievable using Business Rules.

I would highly recommend that you don't repurpose the Leads entity, unless there is a fundamental reason why this would be the preferred option.

Ryan

Was this reply helpful? Yes No
Suggested answer

purwar purwar 2,836 on at

Like (0)

Report

The best solution is :Use only account entity for both vendor & Customer. B/c it will support you in future if you enhance the crm functionality. The proposed solution as below:

1-Use relationshiptype field of account, which have two option Customer & Vender.

2-User Java script to control the account form.

if( relationtype==Vender)

Only vendorrelated fields will be visible on form and required

if relationshiptype==customer)

Customer related fields will be visible on form & required

Was this reply helpful? Yes No