Salesforce Fact #409 | Avoid inconsistency during picklist field update

We know that dependency on the values can the defined between picklists. This is ensured while we are creating or updating records from the UI.

But do you know while creating/updating records from API or data load picklist values can be inconsistent if both the controlling and dependent picklist values are not specified.

In this example, we have two picklist fields on Account: Picklist1 & Picklist2. Picklist1 has two values: valueA, valueB and Picklist2 has three values: value1, value2, value3. The dependency set up is like this: valueA-> value1, value2, value3 & valueB->None.

Now when updating records from the UI, whenever we select valueB, the dependent value sets to None. However, if we update the record from back end specifying only controlling picklist value, only that gets updated & the dependent one remains the same leading to inconsistency. So we should be careful while updating picklists having dependency.

Attached are the screenshots.







Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more