Salesforce Fact #275 | Import field with namespace in LWC

Suppose we have to import multiple fields in LWC of a standard object. Now some of the fields are standard and some are custom fields. The custom fields have a namespace at the start. So, if we try to import them from '@salesforce/schema' it will throw error.

As a workaround, we can refer the custom field Apinames statically and get their value from getRecord.

In this example, we have a custom field AutoNum__c on Account which is having a namespace. So, we have referred the field statically before retrieving its value.

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