New answers tagged

0

I've encountered this, but different scenario. I have a setup where we have two orgs connected via an integration tool. In addition to these two SF orgs, we are connected to an external service. A - SF Org 1 B - SF Org 2 C - 3rd party service B is connected to A & C directly. To save licensing costs if A wants to talk to C it must go through B. This ...


1

You can solve this by placing the second API call in an implements Queueable class. It doesn't work for @future.


0

Here is the coding what i used to solve that, I used contentversion object in salesforce. Attachment attach = [SELECT Id, Name, Body, ContentType, ParentId From Attachment LIMIT 1]; ContentVersion cv = new ContentVersion(); cv.Title = 'Test Document'; cv.PathOnClient = 'TestDocument.pdf'; cv.VersionData = attach.body; //cv.IsMajorVersion = true; ...


0

System.Exception: Regex too complicated is a runtime error that happens for one of two reasons. Either 1) the Matcher is too complex or 2) the Pattern is too complex. I know you're not explicitly creating a Pattern and using a Matcher, but because String.replaceAll accepts a regular expression as its first argument, there are regular expressions being used ...


0

The requestURI used '*https://test.salesforce.com/*' in the RestContext is incorrect. It should point to '/services/apexrest/{URLMapping}'.


0

With the Composite Rest API you can technically retrieve up to 60k records only two request! This is a bit of a cheat in that it relies on "guessing" the nextRecordsUrl of the query and only works without child relationships. In those cases, you can still leverage Composite API to reliably pull down 10k records per query. Doing so would look ...


Top 50 recent answers are included