Yes you will need to create a new page layout/record type if you want to give visibility to one group while hiding it from another group.
So you would have contact record type A: (original layout)
then contact Record Type B: (customized layout)
You then can assign the correct layouts by record type for the profiles you wish to view the new picklist values
We just had the same problem with some clients, and after some digging it had something to do with the Spring 17 release.
Your browser caches assets from the server locally (javascript, css, ...), in Spring 17 a change was made to picklists.js, a javascript file responsible for filling picklist values. In some cases users still had the old javascript from before the release cached in their browser, and that old file doesn't work with the new way of filling picklist values.
The easy way to fix it is by clearing your local files. In chrome you can do this by following these steps:
- Open the page that doesn't show the picklist values
- Open Developer Tools (F12, or right mouse button somewhere in the page -> inspect element)
- Go to the Network tab
- On the top check the "Disable cache" checkbox
- Reload your page
- Uncheck the "Disable cache"
- Close developer tools
If a Salesforce developer reads this:
When your browser tries to load a page which loads a javascript file, it will look at the URL of the javascript file, and then look in the local cache if the javascript file for that URL is present. If so, for performance reasons, the javascript file from the cache will be loaded instead of the remote javascript file.
This can easily be solved by adding a fingerprint to the URL of the javascript file. For example:
<script src="myscripts.js?fingerprint=023UJKdlmamlsqdvNNKKl"></script>
The moment the javascript file is changed (with a new release or whatever), just change the fingerprint, and the file will be cached again locally. (It can be whatever parameter you want, as long as the SRC changes)
Best Answer
TaskSubtype
has a number of special behaviors. It dictates how Activities are displayed on the Lightning Activity timeline, in particular.You cannot add picklist values to the field, and you also cannot update its values on existing records (although you can populate the field in a
before insert
trigger, or when creating records via the API or Data Loader).Basically, like a few things about Tasks and Events, it's magic.