opportunity sales stage classification won't "stick"

Francesca Shiekh 

I had a customer hit this same problem. Basically Sugar has never liked not having 'Closed Won' and 'Closed Lost' in the sales_stage_dom so I presume you do not have those default options, which is hard coded in places to assume those options are there. Chris Raffle is correct that you can update it in the config table on the database to update the classification but from my experience of the case for that customer if you were to edit the list at all it will revert back to all being the open classification.

We have "Won" and "Lost" in sales_sage_dom, but not "Closed Won" and "Closed Lost", if appropriate I'm not opposed to redoing my Sales Stage dom and doing a DB update to replace the existing values wtih "Closed Won" and "Closed Lost" as values.
Frankly I don't recall changing the dropdown, but we've had Sugar since v6 and didn't always understand the consequences of some choices.

Would be nice if the values that are hardcoded in Sugar were not editable/removable  from Studio...

Is it worth the effort to do that cleanup?

Things to note if you do that is that you should also check the following just to check they are not looking for 'Won' as that obviously would need updating

• filters table
• dashboards table
• saved_reports table
• workflow tables (there are a few)
• SugarBPM
• custom code
• sales_probability_dom dropdown list

Of those SugarBPM is the only one that might take a bit to track down the exact table (unless you only have a couple then doing it in the UI is easy enough). I know Sugar expects those hardcoded options for the Opportunity Metrics dashlet on Accounts as well and there might be other places (I suspect Forecasts) but I haven't checked for a while.

Ultimately it depends how much customisation and integration you have with the system. If you don't have any integrating services that would be looking at Opportunities then it probably won't be too much effort to update as most of my list above is database tables so you only need to do some queries. If there isn't much other than standard Sugar stuff personally I would just as it might bite you somewhere else in the future but ultimately if you find lots of references that are going to take you a lot of time then it is up to you if you feel it is worth the time to do.

Sorry I can't give a definitive but it kind of depends on how much pain it is giving you vs the estimated effort based on how many references you find. I think it would be a good exercise to have a look at least to see how much you find and see how much you need to change.

Things to note if you do that is that you should also check the following just to check they are not looking for 'Won' as that obviously would need updating

• filters table
• dashboards table
• saved_reports table
• workflow tables (there are a few)
• SugarBPM
• custom code
• sales_probability_dom dropdown list

Of those SugarBPM is the only one that might take a bit to track down the exact table (unless you only have a couple then doing it in the UI is easy enough). I know Sugar expects those hardcoded options for the Opportunity Metrics dashlet on Accounts as well and there might be other places (I suspect Forecasts) but I haven't checked for a while.

Ultimately it depends how much customisation and integration you have with the system. If you don't have any integrating services that would be looking at Opportunities then it probably won't be too much effort to update as most of my list above is database tables so you only need to do some queries. If there isn't much other than standard Sugar stuff personally I would just as it might bite you somewhere else in the future but ultimately if you find lots of references that are going to take you a lot of time then it is up to you if you feel it is worth the time to do.

Sorry I can't give a definitive but it kind of depends on how much pain it is giving you vs the estimated effort based on how many references you find. I think it would be a good exercise to have a look at least to see how much you find and see how much you need to change.