Salesforce Fact #423 | Error related to owner change

Have you come across errors while changing owner ids of records which involve queues? Let's see few of them.

Error1:


This error happens when you try to assign a queue as the owner but the SObject does not support a queue as the owner. For example, if you try to assign a queue as an account owner by mistake, this error will be encountered since Account object does not support queue as an owner.

Error2: 


This error happens when a queue is supported as the owner for the SObject, but you are trying assign a queue which is not supported by the current object, which supports some other SObject. For example, Case and Lead both objects can have queue as owner. Now, if you try to assign a queue which is supported by Case as the owner of a Lead record, you would get this error.

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