Skip to main content

Random Positive Integer in Salesforce Apex



Here is a code to generate a Positive Number, as parameter this method the the Maximun that can be generated.


Comments

Post a Comment

Popular posts from this blog

Salesforce DX Packages - simple recipe to remove apex classes dependencies

With the recent release of Salesforce DX and the package development model it got me thinking how to avoid dependencies so I can isolate my packages.  Business case The major pain point I saw in the past was around "how to split the metadata so separated teams can work in parallel". For instance, a  team can be one line of business or a stream in a project or a feature.  In the old monologic development approach (AKA "the happy soup") we used to have these big merge sessions in order to integrate and some times re-write incompatible solutions written in parallel by separated teams  (I won't miss those long nights with cold pizza) .  Due to several comments of the merge complexity, Salesforce decided to invest in a better way to allow teams to split their work and this is where the new unlocked packages come into place. However, in order to fully benefit from the  advantages of unlocked packages  we have to deal with ...
Post a Comment
Read more

How to ByPass and Apex Triggers and Avoid Loops

How to ByPass and Apex Triggers and Avoid Loops Sometimes, when developing a trigger from some reasons we need to by pass the a trigger, may, as I mentioned in my previous post " System.LimitException: Too many SOQL queries: 101 ", sometimes we have loops in our triggers logic.  In Other occasions we just want to bypass because records were processed previously. Our first approach for bypassing its to execute an SOQL query to see if record need to be processed or use fields in the object. trigger TriggerTest on User (before insert. before update) { //First go to Database Set ids = Trigger.newMap.keySet(); List relatedObjs = [SELECT Id,Name FROM relatedObject__c WHERE parent__c in :ids]; //Here check which users need to be processed. List UsersToProcess = new List (); for(User usr: Trigger.new){ //Use the values on relatedObjs to validate UsersToProcess.add(usr); } //Process the records if(UsersToProcess.size() >...
Post a Comment
Read more

Salesforce Apex Too many SOQL queries: 101

System.LimitException: Too many SOQL queries: 101 Overview This Exception is thrown when our code goes over the 100 SOQL queries  (Select, Insert, Update, Upsert, Delete) in a single apex transaction. That governor limit is shared between all triggers executed. This means it’s a counter of SOQLs quieres per transaction increased differently by each trigger executed. Therefore we can say that the “Too Many SOQL” Exception it’s a “ Shared blame issue ”. Most common causes that I have seen are due to: „ Triggers are not bulkified. Tigger’s Loops. Features are not grouped efficiently.  Since it’s a “ Shared blame issue ” the exception can be thrown at any place. Maybe not in the trigger or class which it’s contributing the most to the counter. Therefore, to fix it we have to narrow down and validate couple of things. 1.   Verify that your triggers are bulkified. A Bulkified Code, means the code was adapted so triggers can support big number of ...
Post a Comment
Read more