How to design an application in Salesforce to handle governor limit error of maximum 100 jobs in Flex Queue
Recently , I inherited an Org with huge customization , which enqueue 100+ Batch Jobs in few scenario. Now, don’t ask me why ?
I remember, few years back, Salesforce had limit of 5 Apex Batch that can be executed at a time, but we had expectation and demand !!! Salesforce introduced Flex queue and we can have 100 Batch apex waiting to be executed, still we are not happy. After all, human is wanting animal.
If you enjoy watching video then you might enjoy below video where I conducted Live coding explaining basics of Lightning Web Component.
In this post, we are going to Show loading image on initial load of LWC. In background we would be calling Apex class to take decision if loading image should be hided or redirect user to some other page.
Recently, I was in need to update Sales Price (Unit Price) for OpportunityLineItem using Trigger. I wrote a small trigger on before insert and before update of OpportunityLineItem to update Sales Price.
It worked fine on insert however on update, even if user clicked on update button without changing any value, we were getting error Cannot change both ‘UnitPrice’ and ‘TotalPrice’ in update call.
Its Standard Salesforce behavior and seems in background platform tries to perform some calculation for Total Price which is Quantity * Sales Price. I was not able to get it working on before update. However, below two approach worked :
Use Process builder to compute Unit Price as per formula. Process builder field update works after trigger so it went through.
In after update trigger, create list of Opportunity Product to be updates and make explicit update call for all records which qualified for update.
How to use Apex based sharing to share opportunity using Territories
Enterprise Territory management is used to share Account and its related opportunity and Cases.
Account can have multiple Territories.
User can have multiple Territories
Opportunity can have only 1 Territory. Think about it – If Opportunity allowed to have multiple Territory, how revenue would be split between multiple Territory and what would be business rules ?
Territory enables “My Territories” and “My Team’s Territory” filter in Account and Opportunity list View.
While creating Territory, we can decide access to Account, Opportunity and Case. Depending on OWD, access can be private, read only and read write.
Enterprise Territory Management does not support overlay forecast unlike Roles. However we can create report on Opportunity split object.
Overlay forecast (Revenue sharing) is not supported because Opportunity can have only one territory and therefore only 1 revenue maker.
Maximum Territory that can be defined is around 99k unlike maximum role 10k.
Custom Field (but not lookup) can be created in Territory2 object.
Territory related list appears on user and Account records.
You cannot create lookup to Territory objects.
Territory to Opportunity can be assigned using Apex class plugin
Enable Territory based Forecast
Mark user as “Allowed Forecast”
Add user as Territory Team member
Add user as Forecast Manager in Territory
Apex Based Sharing of Opportunity using Territory
For Apex based sharing, we use user of public group Id to share record. If we want to share Opportunity using Territory then there is quick code for that. If we click on manual share button on Opportunity, it will show an option to choose between user, public group, territory and territory with subordinates.
There is no clear documentation, but what I found that when we share using Territory, Salesforce internally creates public group for that territory and assigns that public group to Opportunity.
So, first step is to find public group created for territory. Below code showcase how it can be done.
In last 5 years, web browsers have evolved so much that we need to revisit and check ourselves that do we really need libraries or frameworks for every small functionalities ? Considering rich feature set browsers, Salesforce already revisited aura framework and decided that it’s time to make it more lightweight and use native browser capabilities as much as possible. Welcome Lightning Web Components !!! Before we jump into ocean of Lightning Web Components, it’s important to understand what is supported by browsers natively ? Out of many features supported by modern browsers, one of most important one is Web Component.