Salesforce Fact #794 | Reset value in LWC record picker

We can use the clearSelection() method to reset the value in lightning-record-picker.

Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #218 | Blank picklist value is actually NULL

Image
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.
Read more

Salesforce Fact #929 | Nth highest in screen flow

Image
We can find the Nth highest value in screen flow using Get Records with a bit of logic. For example, we want to find the Nth highest NumberOfEmployees value across all the accounts. The idea is to fetch the records and then run a check to iterate over the records as long as the temp variable value is less than N value. The temp variable is initialized to 1. In the assignment we would keep on removing the first record. At the end, we will pick the first record from the collection. Attached are the screenshots. Note: this is just a POC flow and the error handlings, best practices are not covered.
Read more

Salesforce Fact #989 | New delete files permission

Image
There's a new app permission 'Delete Salesforce Files' has been introduced in Spring'26. It can be assigned using a profile or permission set. This allows the users to delete accessible files irrespective of the ownership. The app permission can be checked in LWC as well similar to other app permissions. Attached is the screenshot. Reference:  https://help.salesforce.com/s/articleView?id=release-notes.rn_experiences_files_delete_files.htm&release=260&type=5 However, there seems to be one issue; With this permission, a user can delete a file with only view access to the file. Hope Salesforce will put further restriction to fix this in upcoming releases.
Read more