Salesforce Fact #353 | Pass value as object structure to child LWC

Suppose we have a use case to pass object like structure data from parent LWC to child LWC. Now, generally we pass individual values considering public property for each of the attribute. But do you know you can pass the data as an object structure as well. This will reduce the number of public properties in the child as the single object structure would be acting as the public property.

In this example, we have simple input fields for capturing the employee name and years of experience and that we are passing as an object structure to the child component.

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