Skip to main content

About sharing that I misunderstood

Sharing means caring literally.In salesforces, with sharing means I want to share based on the rules.

By default, Apex class does not effected by  current user's permissions, field-level security, and sharing rules.Because it run in system context.Oh,please note this is not include Apex code that run in Execute Anonymous.Code in Execute Anonymous still effected by permission of the current user.

So this is the reason why with sharing and without sharing keywords come for.But only to control sharing rules.

Use with sharing to enforce the sharing rules that apply to the current user.

Use without sharing  to ensure that the sharing rules for the current user are not enforced.

How about if the class use neither with sharing or without sharing? Still the current sharing rules remain in effect.

All the details can be check at Using the with sharing or without sharing Keywords .

Actually why suddenly I babbling about sharing?Because it cause me headache  for almost whole day.

I got this one line of code in one Apex class

for (AggregateResult ar : [Select Name, max(Employee) Emp, Account__r.Name AccName  
      from Location__c  Where Account__c != null and Status__c = 'Approved' 
       group by Name,Account__r.Name order by Name])
  system.debug('@MYTEST Name=' +(String)ar.get('Name')+' , Account Name ='+(String)ar.get('AccName'));

The issue that I face, when ever I run my application the Account Name returning null value while actually I knew it should return some value.

I run the query in Workbench , it 's returning the data.I run in Developer console, it also returning data.But when I try to execute it from UI,the value not coming out in Monitoring Debug log.

I never thought the issue is caused by this sharing stuff.After struggling whole day, I discussed with my colleague and she suggesting to remove with sharing  keyword from the class.

After I have done that, my problem puff away.The value printing as usual.Now I can see that with sharing is not mean sharing is caring or you can share the data to everyone.It means, the sharing will be restricted or  can say that actually I can put it if I want to share certain data only.

Use with sharing when you only want to share certain thing.If you want to share it to all,do not use with sharing.


Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {