Salesforce Facts by Abhishek

For new users, we can use the System.setPassword() method to set a password and while logging in they would be prompted to set a new password as per the standard salesforce behavior. However, clicking on cancel would bypass that and would login to the org. This is helpful while creating multiple test users in bulk and to have same password for all instead of manually setting it for each user. Reference:  https://salesforce.stackexchange.com/questions/83345/how-do-i-create-a-user-without-asking-them-to-set-their-password

While using the lightning app builder, we can open another app/home/record record page in same tab. Go to Pages dropdown -> Open Page -> Search for the page you want to open -> select the page -> Open. Attached is the screenshot.

While creating a new user from UI, the IsActive checkbox is true and cannot be edited. However, while creating users from CSV file or API, we can set the IsActive flag to false to create the users as inactive.

Sometimes we want the login as option to be restricted for one particular user like the integration user or deployment user in the org. We can create a transaction security policy on LoginAs event to impose the same. Note: The user Id should be 15 digit Id in the condition Attached is the screenshot.

We need to be careful while using the IN operator in Get Records element in record-triggered flow. If the text collection is empty, it seems Salesforce runs a query to fetch all the records of that sobject and the number of query rows are counted in the governor limit. So, if the total number of records for that sobject is more than 50000, it throws limit error. Fix would be to always check if the collection is empty or not, before using it in the IN operation. In this example, varIds is an empty text collection used in IN operation to fetch the account records. However, the number of query rows returned is 136 instead of 0, which is the total number of account records in the org. Attached are the screenshots.

Steps to delete debug level: Go to classic -> setup -> Under Monitor -> Logs -> Debug levels -> select the debug level -> delete. Reference:  https://stackoverflow.com/questions/73911362/salesforce-debug-levels-need-to-edit-or-delete-existing-level