Posts

LinkedIn

Send Data from Salesforce to Data Cloud using Ingestion API and Flow

Image
As part of this blog post, we are going to see a Sprint 24 feature - Send Data to Data Cloud using Flows and Ingestion API. The release note is available  here .   Introduction As we all know, Data Cloud helps us to build a unique view of customers by harmonizing data from multiple source systems and coming up with meaningful data segmentation and insights that can be used in different platforms for additional processing.  If you ar e new to D ata Cloud refer to Salesforce documentation or these videos that are part of Salesforce Developers youtube channel. What is Ingestion API As per Salesforce documentation ,  Ingestion API is a REST API and offers two interaction patterns: bulk and streaming. The streaming pattern accepts incremental updates to a dataset as those changes are captured, while the bulk pattern accepts CSV files in cases where data syncs occur periodically. The same data stream can accept data from the streaming and the bulk interaction. This Ingestion API will be he

Salesforce Record Triggered Flows - Create custom error messages

Image
  1. Introduction As part of Winter 24 release, Salesforce released this much-awaited flow feature by which we can fire custom error messages to users as part of record-triggered flows. This feature is available as part of both before and after save record triggered flows. We can add error messages to a specific field or at the page level. Let us see 2 use cases to demonstrate this feature. 2. Use case 1 - Before Save Flows Scenario - When an Account is getting deactivated and if there are any active Contacts under that Account, deactivation should be failed with a custom error message. Implementation steps: 1. Create an isActive checkbox in contact 2. Create a before record triggered flow in Account to check for active contacts when Account Active value becomes false: Add entry criteria as Active field update:  Now fetch active contacts under that Account: Now add a decision element to check if the count >0 if a contact exists add custom error we can see Custom Error available as a

HTTP Callout from Salesforce Flow - Without Using Code

Image
 As part of the Spring 23 release, Salesforce introduced a beta feature, using which we can make HTTP callouts from flow without writing a single line of code. This is definitely great news for all the flow lovers. Let us see this using a Google Blogger API. 1. Introduction I want to consume Google Blogger API in a screen flow to see my blogger-related details. Let us see the step-by-step approach to set up this 2. Google API Access Set Up 1. Open your Google console   2. Create a new project 3. Open the Consent screen from Navigation Menu and do the basic set up 4. Add the basic detail including the App name, developer email, test user, etc and create the App 5. Once consent setup is completed, go to Credentials and create a new credential 6. We are going to consume OAuth authentication 7. Give a name for now and save it. We can update other details later. 8. You can see your client id and client secret. Take note of these values 9. Next step is to enable Blogger API for consumption F