Salesforce Fact #188 | Be careful with current user Id in flow

We need to be careful while dealing with current user Id from the $User global variable in flow. It returns the case sensitive Id of 15 character length. So during the Id comparison we may experience discrepancy, as the standard userId storing fields in object stores the Id in 18 character case insensitive format.

Therefore, in the flow we can use a formula field and store the current user Id after applying the CASESAFEID function to get the equivalent 18 character version.

Attached are the screenshots.








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 #947 | Resolving dashboard logged-in user limit error

As we know there's a limit on the number of dashboards with the option to run as the logged-in user, the below queries are useful while troubleshooting and resolving the error: SELECT FolderName,Title FROM Dashboard WHERE Type = 'LoggedInUser' OR Type = 'MyTeamUser' -> This will fetch the list if dynamic dashboards present in the org SELECT Id,Title FROM Dashboard WHERE Type != 'SpecifiedUser' -> This will return dynamic dashboards that are not in private folders.  SELECT Id,Title FROM Dashboard USING SCOPE allPrivate WHERE Type != 'SpecifiedUser'  -> This will return dynamic dashboards that are in private folders. Reference:  https://help.salesforce.com/s/articleView?id=000385369&type=1
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