search

SFDO-Community / OmbudsmanCloudCare

App for Navy ombudsmen to track, resolve, and report on cases.
BSD 3-Clause "New" or "Revised" License
10 stars 5 forks source link

Case Standard Picklist Values Inactive #30

Closed mkolodner closed 4 years ago

mkolodner commented 4 years ago

Just noticed that Case Reason in a new scratch org includes the original standard picklist values (Installation, Equipment Complexity) that we would like to disable. Plus Red Cross Message, a new value I am sure I added several days ago, is not there. I am obviously capable of adding Red Cross Message to the repo, but wanted to note it in case someone knows why it didn't stick.

mkolodner commented 4 years ago

I see Red Cross Message in the repo under Pre/standardvaluesets/standardvaluesets/CaseReasonstandardvalueset right alongside the other options. So I don't understand why it's not in the org I just spun up? Actually, I spun up another scratch org and in that one all of the OCC reasons are inactive picklist values AND Red Cross Message is missing. What am I missing @Nickers3 ?

mkolodner commented 4 years ago

This applies to all Case picklists. The values seem to deploy but not be made active and the standard values remain active. @Nickers3 may have seen a case where some values deployed and some didn't?

Nickers3 commented 4 years ago

Resolved with with changing package.xml file and standardValueSet folder names. Did learn we should use add_standard_value_set_entries in place so will resolve with issue #34