I went to YouTube and I did not find much of a discussion on the recent data breach incidents. I think it is very important we discuss these incidents and prepare our orgs for potential threats. Here is a video I made explaining my take:
How Did Hackers Steal Salesforce Data?
https://youtu.be/fEMeBiR6IY4#Security #External Service #External ApplicationJust got notified about these urgently implemented changes a few days ago. Good to see some actions are being taken!
When I try to create a new external service as it is indicated in that trailhead, I get this error:
An error was encountered while trying to retrieve the service schema.
On the Named Credentials page, you need to click New Legacy instead of New.
In Salesforce External Datasource we are trying to Consuming Mule Application via Odata. As part of this, client requirement is for one of the field datatype is IndirectLookup which links to Opportunity Table field. In Mule 4, while creating odata raml, i need to know how to handle IndirectLookup datatype. I tried with datatype as text it failed as below field type doesn't match. In Salesforce : "IndirectLookup". In data source : "Text". Please let me know fix for it. Thanks
#MuleSoft #External Service #Salesforcecommunity #Salesforce #Metadata
Hi @satish Lingamgunti, please remember, this group is to help you learn how to navigate in the new Trailblazer Community.
Please see this helpful post which explains how to create a question on the TBC!
When I try to debug the flow, I got this Error.
Hi @Pratik Patil,
These errors can be hard to debug. The best way to get a quick turnaround on this.
First Method: Set-up the debug log for the user who is getting this error.
Try to reproduce the error and analyze the debug log to check the root cause.
Second Method: If the debug log won’t give you much information about this error then you have the only way to resolve it in less time which is to log a case with Salesforce support.
Please share the below information on your case to get a quick response on it.
Support will track the stack trace at your org instance try to find out the root cause of the error and suggest the appropriate solution for the error.
The above information will help them to filter out the server logs.
If still facing errors kindly share the flow error screenshot along with the error screenshot.
I hope this helps!
Thanks
Saurabh
I'm using External Services with Flow and the repsonse I'm receiving back from the 3rd party system isn't being accepted for some reason. All the fields are mapped successfully
Dummy data below
Unable to map response for output parameter 200 of invocable action SFRequestPersonDetailsv2.SFRequestPersonDetailsOperation. Received response: {"ResponsePersonDetails":{"Person_Reference":"25161614990003","Title":"Mr","Other_Title":null,"Forenames":"David","Surname":"Office","Date_of_Birth":"1893-02-07Z","National_Insurance_Number":null,"Deceased":false,"Date_of_Death":null,"Home_Tel":null,"Mobile":"07805198","Work_Tel":null,"Email":"office.david@gmail.com","NoK_Name":null,"Nok_Contact_Details":null,"Relationship":null,"OnTenancy":true,"MainContact":true,"TenancyReference":"20109671"}}
I can't understand why the values aren't being accepted
I saw that, but the only solution suggest was something about special characters. It doesn't explain why it was working a few days ago.
But, then I noticed a 'Z' a the end of the date field. No idea why that suddenly started being sent by the 3rd party system.
So, in summary. it was data being sent in the incorrect format
Integrate APIs Faster and Effectively with External Services
Ready to integrate faster? Learn about External Services, a feature that transforms OpenAPI end points into invocable actions that you can call from low-code tools and also from code.
Session Materials - coming soon (9/14/23)
If you're familiar with the Twilio Verify API, it uses basic authentication to send a One-Time PIN, and there is no token process. In order to use the Twilio Verify API as an External Service, I had to create a Legacy Named Credential that uses Anonymous Authentication. To further complicate things, the basic requirements are to send a URL Encoded 'To' address (phone number/email) and 'Channel' (SMS, Email, Phone, WhatsApp).
I wrote a quick RAML and posted it in our Mulesoft API Exchange, it imported nicely, and I'm able to add the Auth parameter and ServiceID, but I can't get any parameters to show up in the Flow Action for the 'To' and 'Channel' values. It's a pretty weird use case, not exactly fitting current External Service functionality, but any insight is welcome!
Dug through this with one of my Salesforce SMEs. Here are the fixes:
For whatever reason, defining responses in the API spec caused Salesforce to fail parsing the response every time.
I'm getting a very non-specific error when I try to import an API from our Mulesoft API Gateway. Any idea what's causing this? I suspect it's because the URL is blank on the import page, but I have a BaseUri specified in the Mulesoft Exchange RAML. What am I missing?
#Enhanced External Services #External Service #Use External Services #MuleSoft Integration
There is an issue with how our Enterprise writes our OAS. We are only using Mulesoft Gateway Proxy, and importing our OAS to be used in the Mulesoft Exchange catalog. Each of our OAS generating the error would need to be rewritten to comply with the specific Mulesoft formatting needed by the connector.
Salesforce Summer 22 Development Features You Can't Miss Welcome to #Summer22Treasure ! In this release, you will find lots of new features and new enhancements related to Lightning Experience, Salesforce Flow, Lightning Web Component, Apex, Experience Cloud, and APIs. In this video, I have focused on some of the powerful, important development features which we all should know as this will help us to write more secure and effective code. #Release Readiness #External Service #LWC #LWC Development ▬ Contents of this video ▬▬▬▬▬▬▬▬▬▬ ✅ - Secure Apex Code with User Mode Database Operations (Beta) ✅ - Overloads Aren’t Allowed on @AuraEnabled Methods ✅ - Call Invocable Actions from Apex (Developer Preview) ✅ - Call External Services Registrations from Apex ✅ - Call External Services Registrations from Flow
Youtube Link: https://youtu.be/jQxR8bwjT54
@The Blog Group @Developer Group, Kitchener, CA @Admin Group, Jaipur, IN @Kolkata User Group @Kolkata User Group, India @Toronto Salesforce Developer Group @Admin Group, Bikaner, IN @* Release Readiness Trailblazers *@New Delhi User Group @* Salesforce Administrators *@* Salesforce Developers *@Developer Group, Dhaka, BD
I am trying to use Klaviyo API using External Services. The Open API Schema for this API is https://klaviyo-openapi.s3.amazonaws.com/spec.json. I am able to create External Service and used API https://a.klaviyo.com/api/v1/metrics/timeline in flow. This API is being called but it throws an error Unable to map response for parameter: 200 and invokable action: KMetric.metrics-timeline. I can see that JSON has a few properties which started with a $ character. Not sure, this could be the reason for this error.
Any thought on this issue?
#External Service #Ask An Expert @Kris Harrison @Andrea Guzman @Liz Skaates
Hi @Dhanik Sahni - thanks for reaching out. This issue might be a bug where special characters aren’t encoded right. Can you please submit a support case with these details share the case number so I can track it.
Also, in the meantime, I'd encourage you to take a look at this post, which might help you debug the issue in the event this is not a bug.
