Mike
Sat Feb 18 12:20:13 CST 2006
I don't have a specific one, I was looking to see what others are doing as a
general rule.
For example as a systems integration shop, we will want to track support
calls by product. So how granular do you get, is it better as a hierarchy
that is 4 levels deep, 10 levels...
Lets say for support calls would we be better with subjects like this;
Products
Microsoft
Office
(SPS) SharePoint Portal Server 2003
(WSS) Windows SharePoint Server 2003
Office XP
Office 2003
Outlook
Word
Excel
SQL Server
SQL Server v7.0
SQL Server 2000
SQL Server 2000 Reporting Services
SQL Server 2000 Analysis Services
SQL Server 2005
(SSRS) SQL Server 2005 Reporting
Services
(SSIS) SQL Server 2005 Integration
Services
(SSAS) SQL Server 2005 Analysis Services
Windows Server 2000 Standard
AD
DNS
WINS
IIS
File and Print
Replication
Windows Server 2000 Enterprise
AD
DNS
WINS
IIS
File and Print
Replication
Windows Server 2003 Standard
AD
DNS
WINS
IIS
File and Print
Replication
Windows Server 2003 Enterprise
AD
DNS
WINS
IIS
File and Print
Replication
Trying to find the balance of not enough detail, too much detail
Thanks again, Mike
"John O'Donnell" <csharpconsulting@nospam-hotmail.com-nospam> wrote in
message news:%23l4iG2rMGHA.1760@TK2MSFTNGP10.phx.gbl...
> There is no right way or wrong way however I would not usually use a one
> level subject list.
>
> Might help if you could describe your particular scenario
>
>
> =======================
> John O'Donnell
> Microsoft CRM MVP
>
http://codegallery.gotdotnet.com/crm
>
>
>
>
> "Mike Morisoli" <michael@nospam-vieon.net> wrote in message
> news:OpSC4PaLGHA.2276@TK2MSFTNGP15.phx.gbl...
>>I was wondering if anybody would like to share how they are using Subjects
>>in CRM.
>>
>>
>>
>>
>> I am trying to decide if you are better with a flat list of basic
>> subjects or a nested list of highly granular subjects. Interested in
>> what others are doing, what has worked, what has not.
>>
>>
>>
>>
>> Thanks in advance, Mike
>>
>>
>
>