Salesforce Facts by Abhishek

In order to get the current user id in IP, we can use a Set Values element and populate the value:  =%$Vlocity.UserId% in one attribute. And in subsequent elements we can get the value similar to the below syntax: %SetCurrentUserId:currentUserId% here  SetCurrentUserId is the Set Values element name and  currentUserId is the attribute name.

Here's one approach to find out the account names with no related contacts using DataRaptor Extract. Attached are the screenshots.

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.

Suppose we have a requirement that a radio button needs to be selected by the user in the current screen. Once the user moves previous/next from the current screen, it should get disabled. We can implement this using screen action and bit of condition logic. We can add condition to make sure the screen action autolaunched flow is called only once. And we can create a formula resource to check the InProgress and IsSuccess property of the action button which is used in the disabled attribute of the radio buttons. Attached are the screenshots.

The 'Skip the matching records' option flow Upsert operation is pretty helpful. If this option is selected, the flow first fires a SOQL to find out the matching records and if any found, skips the Create DML. This is not the case in Apex and in case of Upsert, it always fires the DML regardless of the record's existence. Attached is the screenshot.

Suppose we have a requirement to keep track of the first selected radio button in screen flow. For this, we can create an autolaunched flow and call it as a screen action. This flow will accept the first selected value and assign to a variable. We also need to set the action run condition in a way so that the subflow is called only once. In this example, we have a radio button with three values: Option1, Option2, Option3 and in the action run condition we have specified to call this flow till the currentValue resource is null. Attached are the screenshots.