Issue: Duplicate (blank) versions are created when deploying a Flow with Change Set

Tags

I tried deploying the flow to Production org using Change Set and the flow was modified in my Sandbox Org. After deployment, Salesforce created 2 versions of the flow in Production org and one was blank. When I searched in google, I found out that this is one of the known issue. Here are the details and you can subscribe to this link, if this issue affects you so that you will be notified by Salesforce when the issue is resolved. Thanks!

Tip#20 -Restricted Picklists

Tags

,

A restricted picklist field includes only the values that you’ve defined and users cannot enter any value other than the defined picklist values. This is to ensure that the integrity of the picklist data is maintained and your picklist stays clean. Salesforce has introduced this functionality in Spring’16 and it is in Beta.

If you have a Developer Edition org or sandbox org, no setup is required to use restricted picklists. For all other editions, restricted picklists are available as a beta feature, which means they’re highly functional but have known limitations. Contact Salesforce to enable restricted picklists.

Suppose, you have configured a restricted picklist in Sandbox and when you move it to production, you might get an error “Cannot have restricted picklists in this organization.” To resolve the issue, you can contact support to enable restricted picklists in production org.

Here you can find the release notes from Salesforce.

Extract Controlling and Dependent picklist values

Tags

, ,

If you ever want to print or extract Controlling and Dependent picklist values, you can use the solution highlighted by Kenny Jacobson

here is the link

I had to use it in my current project to check the field dependencies for 2 picklist fields and make modifications accordingly.