Microsoft CRM 4.0 modifying states for an opportunity

I need to add a State of Closed besides the Won/Lost.  Is there a way to add a State Value?
sjmeiners11Asked:
Who is Participating?
 
Chinmay PatelConnect With a Mentor Enterprise ArchitectCommented:
If you are putting in a Closed state you can put it in lost, but when you are creating reports or any other representation, based on that custom field you will ignore whether this particular opportunity is won or lost.
0
 
processguruCommented:
No, you can only edit the statusreason of Won or Lost. Generally everything will fit in one of those buckets. If it does not really fit in one of those buckets, you can use filtering in your reporting to be sure you don't include the particular status reason in your win/loss analysis.
0
 
sjmeiners11Author Commented:
I was hoping for a different answer as you might expect.  The problem is when you are running the analysis depending on what level of the organization you are you may not know that there are reasons that are in these 2 status codes that really don't fall under Won or Lost.  Numbers can get very crazy.  

Thanks
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
processguruCommented:
I'm sorry, I think I'm lost on your last comment. Can you give me an example where you want this Closed state and what entity it would be on?

I understand your disappointment of course...
0
 
Chinmay PatelEnterprise ArchitectCommented:
In that case I would suggest to put in a custom field to indicate the Closed state. Not very practical but then it is a sure shot way to identify those records which does not fall in Won or Lost.

Regards,
Chinmay.
0
 
sjmeiners11Author Commented:
Chinmay what would the status code be if we did it that way?  Do you think it would be blank?
0
 
processguruCommented:
You cannot have a blank state code. It will always be one or the other.

What entity are you working with? And what is the business case that is driving this requirement?
0
 
sjmeiners11Author Commented:
processguru - I am in the Opportunity Entity.  In our business an opportunity can be Won, Lost or Closed (due to business timing not because you actually Lost the opportunity.  You never really had the chance.)  So when a corporation is running their won/lost analysis you don't want these records to show up as Lost.  They really weren't Lost at this point and unless you are directly involved you won't know that.
0
 
processguruConnect With a Mentor Commented:
I have often seen in this situation handled with a Cancelled status reason under the Lost state code. It makes more sense for it to be in the Lost bucket than Won, because you will not be getting revenue out of the opportunity. However, when you build your Loss analysis reports, you handle all those with Canceled as the status reason separately - either ignored, or counted in a different way. This is a very standard business process. Those 'canceled' or 'closed' will generally not have any competitor information logged against them, and are not included in any analysis as to areas for improvement in order to win more business, etc.

It all really comes down to how you build your reports/views/charts, etc. In any way that you display this information you can always disregard these 'canceled' or 'closed' opportunities so that there is no confusion. It's all about smart presentation of the data to the user.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.