Salesforce

What is GraphQL?   GraphQL is a standard query language for APIs and a runtime for fulfilling those queries with your data. It provides users with a single endpoint to request all necessary data from in a single request. Applications that utilise GraphQL APIs are frequently far more efficient than those that stick with REST APIs. This is due to their capacity to retrieve all required data in a single invocation, which reduces the number of round trips to the server, allowing you to customise it to meet your needs. Why GraphQL is better than REST API? REST API is the gold standard for APIs, yet traditional REST APIs present significant issues when developing modern, highly performant, and scalable online and mobile applications. REST endpoints do not allow client changes to the API endpoint's response.   For example, when fetching a user's phone number from a REST API, receiving extraneous data beyond the number adds unnecessary costs for both the server and the requester. ...

If you don’t know the basics of SOAP fear not, because I've got you covered! Dive into the basics of SOAP with my latest blog, ' SOAP Explained: With JavaScript .’ Oh, you already know about SOAP and are here to learn how it works in Salesforce? You've come to the right spot! Let's get started. SOAP Integration in Salesforce SOAP is a protocol where client and server are tightly coupled meaning that minor changes on either side can potentially disrupt the connection.   To use SOAP API, your org must use Enterprise Edition, Performance Edition, Unlimited Edition, or Developer Edition. In all supported editions, a user must have the API Enabled permission turned on in the user profile they’re assigned.  In Salesforce, Apex SOAP web services(It is like a class) allow an external application to invoke Apex methods through SOAP Web services. The Web service that is available to you is defined in generated WSDL file. What is WSDL? Web Service Description Language is a file t...

Last Updated: 09-11-2023   Let's define the terms we will use in this blog post: Source org - The org that has all the files. Current org (destination) - The destination org where all files are to be fetched from the source org. Because all code will be written in the destination org only; no coding will be done in the source org. To upload files from one Salesforce org to another using Salesforce REST APIs, you can follow these general steps:  Get Session Token , Org Base URL of source org. Get Record Ids from which we need to get the related files. Hit the  Salesforce REST APIs to fetch the files from source org.  Create Content Version in current org (destination). Create Content Document Link in current org (destination) which will associate the file with the record you want. Before going to code let's make our current org ready, we will create 2 fields in our object level  Ext_Record_Id__c - The record id of the record in the source org that we need to...