Salesforce Fact #218 | Blank picklist value is actually NULL

Whenever we are setting any picklist field value to blank, it will get stored in database as NULL. So we need to be careful while processing this data after fetching from database.

In this example, we are creating an account in a test method with type as blank, and populating blank using single quotes instead of NULL. Now after we fetch the data from the database it is NULL, not blank.

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