Salesforce Fact #383 | Issue while using current record audit fields in lookup filters

We should not use audit fields of the current record in lookup filter criteria. Since, the audit fields are populated once the record is created, using them in lookup filters will cause issues during creation of the record. As the record is not created yet, the filter won't be able to fetch any data.

In this example, we want to put a filter that the users can select the account records which are created by them i.e. the created by Id of account and contact record would be same. Although this filter would work for existing records, it won't get any data during creation of a new contact.

Attached is the screenshot.



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