Modify drop-list of SUGAR on Revenu Line item

Hi Phuong Trinh ,

We regularly modify the sales stage and probability settings for our clients, so it should not be an issue to make the modifications via Studio. I have not encountered the SQL error you are seeing. It looks like there may be a misconfiguration in your dropdown lists. To validate, please go to Admin >  Dropdown Editor and provide screenshots of both lists (sales_stage_dom & sales_probability_dom) as they show there.

Chris

Hi Chris Raffle 

Here are the screenshot : 

Sales_stage_dom

sales_probability_dom

Thanks for your reply quickly :) 

Best regards,

Phuong

Hi Phuong Trinh ,

For some reason, all of your statuses are classified as 'Open' (Ouvert) statuses. Click on the pencil icon for 'Closed Won' and 'Closed Lost' and changes the status to the corresponding 'Closed' status:

Once you make those changes, save the entire list and see if the SQL error still occurs.

Chris

Hi Chris, 

I've tried for many times to change the statuses 'Close Won' and 'Close Lost' to 'Close Won' and 'Close Lost' but when i save this changes, Sugar didn't to save it, it still stays 'Open' as status for all the Sale stages.... 

Hi Chris, 

I've tried for many times to change the statuses 'Close Won' and 'Close Lost' to 'Close Won' and 'Close Lost' but when i save this changes, Sugar didn't to save it, it still stays 'Open' as status for all the Sale stages.... 

Hi Phuong Trinh ,

That's odd behavior. These values are stored at the database layer, so I'm not sure why it would fail to update. Please do the following:

1. Go to the Custom Queries module to create a new query (e.g. https://<your_sugar_URL>/#bwc/index.php?module=CustomQueries&action=EditView&return_module=CustomQueries&return_action=DetailView)
2. Give the query a name and put the following query in the Custom Query box:
   

   SELECT 
       * 
   FROM 
       config 
   WHERE 
       name IN ('sales_stage_won', 'sales_stage_lost');

3. Click 'Save'
4. Click 'Run Query' for the query you created

If the query returns any results, post them here. If you don't get any results, run the following query on your database:

INSERT INTO 
    config (category, name, value, platform) 
VALUES 
    ('Forecasts', 'sales_stage_won', '["Closed Won"]', 'base'),
    ('Forecasts', 'sales_stage_lost', '["Closed Lost"]', 'base');    

Note: If you are hosted in Sugar Cloud, you will need to open a support case for them to run the above query.

Once the query is executed, go to Admin > Repair > Quick Repair & Rebuild, then check the dropdown list to see if it properly reflects the categorizations. 

Chris

Hi Chris, 

I've tried your query and here is the result : 

The result seems strange to me, What do you think ? 

Do you think that i must open a support case and ask to run the 2nd query ? 

I've already open a case with SUGAR Support, they think that our problem is similiar to issue #90615 https://portal.sugarondemand.com/#supp_Bugs/90615. 

If there is no solution quickly (cause i've implemtent the case in our instance prod...), i have to ask Support to restore the backup of our instance prod before this monday. I'm affraid that will cause trouble for our current data  because of this changes in drop-down list.

Thanks for your opinions. 

Have a good day

Phuong

Hi Phuong Trinh ,

I agree that the bug they reference does seem like a potential culprit. My recommendation is to try the documented workaround in the bug (i.e. change the dropdown list language to English and modify the Closed Won/Closed Lost property). If that still doesn't work, then please have Sugar Support run the following queries:

UPDATE 
    config 
SET 
    value = '["Closed Won"]'
WHERE 
    name = 'sales_stage_won';
    
UPDATE 
    config 
SET 
    value = '["Closed Lost"]'
WHERE 
    name = 'sales_stage_lost';

Chris

Hi Chris, 

Thank you for enlightening me.

I’ve tested the proposed workaround, but unfortunately, it’s still not resolving the problem. I’ve requested Support to execute the SQL queries if no progress is made on their end.

The last update I received was their acknowledgment of the bug #9061, but the response time has been slow. Meanwhile, we’re facing a critical risk of losing data if we can’t fix this issue promptly. In the worst case, we’ll need to restore data from Monday morning, which is far from ideal.

I’d appreciate any advice or support on how to expedite this process or alternative solutions to consider.

Thank you Chris,

Have a good day

Hi Chris,

Our issue is solved (finally). I'm so happy for that ! And of course thank for figuring out why it doesn't work. 

Best regards. 

Phuong