Posts

Showing posts with the label Access

Salesforce Fact #941 | Selective Sandbox Access

With the Winter'25 release, we now require to select a public group while creating a Developer or Developer-pro sandbox.  This feature has been termed as 'Selective Sandbox Access'.   This helps to provide access to the new sandbox to a group of users removing the tedious work of removing .invalid from the user's email. Users outside the public group would remain frozen. Reference:  https://help.salesforce.com/s/articleView?id=platform.data_sandbox_selective_access.htm&type=5

Salesforce Fact #892 | Parent record access missing in LWC getRecord

Image
While using getRecord in LWC, if the user does not have access to the parent record the parent field values are shown as null but there is no error encountered. In this example, we have an Account lookup on Lead record and fetching the Rating and Account Owner name using getRecord. Attached are the screenshots.

Salesforce Fact #875 | Checking custom metadata access in PS

Suppose we need to find out which all permission sets have a particular custom metadata access enabled. For this, first we need to find out the object Id of the custom metadata and using that object id we can get the list of permission sets. In this example, first we are getting the object id of the custom metadata. This can be obtained either from the url or by querying the CustomObject as below: SELECT Id FROM CustomObject WHERE DeveloperName='Parent_Metadata' Next, we query on SetupEntityAccess like below: SELECT Id, Parent.name, SetupEntityId, SetupEntityType, SystemModstamp FROM SetupEntityAccess WHERE parent.isownedbyprofile=False AND SetupEntityId IN ('01I6F000003cdLBUAY')

Salesforce Fact #693 | User access policy in action

Image
User Access Policies is now in Beta phase. Thanks to Summer'23 release. Now, you can automate the Permission Set, Public Group or queue assignments once you create or update the any user which matches a particular Profile/Role/Permission Set condition. In this example, we have setup a User access policy which assigns the PS 'Test Permission Set' and Public group 'Test PG1' if the user with profile 'Test Profile' is created/updated. Note: There are couple of statuses available while configuring User access policy. It gets executed only if it is in 'Active' status.  In order to enable the feature, go to User Management Settings -> Enable 'User Access Policies (Beta)'. Attached are the screenshots.