Salesforce Geek

Looking for Salesforce Training & HandsOn Projects? Trailblazer Profile  |  LinkedIn  |  Salesforce Blog  |  Facebook  |  Youtube Channel  |  WhatsApp Community Composite resource offered by Salesforce allows used to execute a series of REST API Requests in single call. Each of the child request is called as Subrequest. After the execution we will get Response Bodies & corresponding HTTP status for each subrequest with in the same call. Using this design pattern has a huge advantage of reducing number of API Calls to Salesforce. Since the whole series of requests counts as single call towards the API Limits. Possibilities are limitless so plan your solutions using the best design pattern at hand for the given piece of problem. In this blog we will discuss the implementation of “Composite/Batch” design pattern to solve a business problem. To start with this demo I am having a scenario where I need to Post some “Invoices” and “Payments” for a Customer, also need to ret

Looking for Salesforce Training & HandsOn Projects? Trailblazer Profile  |  LinkedIn  |  Salesforce Blog  |  Facebook  |  Youtube Channel  |  WhatsApp Community Documenting development artifacts are as critical as writing code for them and this fact holds well no matter in which technology stack you are dealing with. Salesforce also is no exception to this. In this article, we will discuss and see the implementations of the Aura Documentation Framework, which is a well-managed approach recommended by Salesforce to document the functionalities & behavior of Aura Components, Apps, Attributes and much more. Aura Documentation Framework is hugely dependent on the inline description capabilities of lightning tags. Few of them are ”<aura:application>” ,“<aura:component>”, “<aura:attribute>”,”<aura:event>”,“<aura:interface>”,”<aura:registerEvent>” . To start with the demo I have a simple component that I have developed earlier. I am going to

Looking for Salesforce Training & HandsOn Projects? Trailblazer Profile  |  LinkedIn  |  Salesforce Blog  |  Facebook  |  Youtube Channel  |  WhatsApp Community SObject Tree is another powerful Composite Resource implementation that can enable you to build efficient API Requests to Servers which results in an efficient solution and a happy Customer.   Using this approach we can create a single API request that holds a set of “POST” executions for up to “5” different Object Type that’s all in one go. Awesome.   No more multiple to and fro between Client and Server, just fire and forget.   This approach can hold “5” different Object Trees (One for each object type) that can hold up to “200” records to work upon across all Object trees. Each Object tree can hold nested records based on Parent-Child relationship and this nesting can go up to a maximum of “5” levels.    The entire request counts as a single call toward your API limits. So the arena is open. Run you