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

Change format for standard picklist values being deployed #39

Closed Nickers3 closed 4 years ago

Nickers3 commented 4 years ago

Critical Changes

Change from standard value set deployment from unpackaged to add_standard_value_set_entries task.

Changes

Issues Closed

34

Nickers3 commented 4 years ago

@mkolodner running a test dev_org flow to confirm this works. With this change, we cannot remove (deactivate) the picklist values. This is a best practice per HUB post. Would need to build documentation to ask for deactivation. I think Case Reason is the only one this affects.

mkolodner commented 4 years ago

As annoying as it is, I understand why we can't deactivate values--I saw the Hub discussion. (It would be nice, though to have a way to have the scratch orgs not require that manual work every time.) I was just running a dev org test to see about the email address change and for some reason the flow looked like it ran with no errors, but my org had none of the OCC app in it. I've killed that scratch and am running another too see if it repeats. But that was weird.

Nickers3 commented 4 years ago

I noticed NPSP does this for contact roles with the config folder so I'll add it there. Running a test flow to confirm and will merge.