Creating a Subject Tree in Microsoft Dynamics CRM 4

I am looking to set up the subject tree in Microsoft Dynamics CRM 4.0.  My question is in regard on how to structure the subject tree.  

We currently have a number of general product groups within our company.  For example,

- Air Filters
- Gas Filters
- Drain Valves
- etc.

Within the CRM Subject Tree, should I have a parent subject called "Products" and then all of the product groups as children of that parent.  Example:

- Products
     - Air Filter
     - Gas Filter
     - etc.

Or should I just use each of the product groups as the Parent?

My concern is if we ever need to create another "Parent" within the Subject Tree (such as Service) then it would be nice to have a simplified grouping at the Parent level within the Subject tree.

Thoughts?
csimmons1324IT ManagerAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Feridun KadirConnect With a Mentor Principal ConsultantCommented:
Looks good to me.
0
 
Feridun KadirPrincipal ConsultantCommented:
I'm not a fan of having many levels in the Subject Tree, because in forms you only see the wording for the level that you selected.

I think you need to take a view on subjects that you might need in the future and allow for them without changing what you do now.

Also, consider in which parts of CRM you will use the subject tree. Is it just cases or perhaps products as well or somewhere else? Someone else might have an idea for subjects.

For the scenario that you presented, I think the Parent approach is probably the best.
0
 
csimmons1324IT ManagerAuthor Commented:
feridun,

I envision using the subject tree for products, cases and KB articles.  I am leaning toward designing the tree like so:

- Air Filters
     - Model AF100
     - Model AF200
     - Model AF300

- Gas Filters
     - Model GF100
     - Model GF200
     - Model GF300

- Drain Valves
     - Model DV100
     - Model DV200


If my thought process is correct, this will then allow the user to select the proper model number of the item that that they are referencing, whether they are creating a product, case or KB article.  It will also allow for greater detail when doing reporting or finding all information (products, cased, KB articles) related to a specific model.

Thoughts?
0
All Courses

From novice to tech pro — start learning today.