How to be able to process a large JSON response?2019 Community Moderator ElectionDeserialising a JSON...
Modern Day Chaucer
How can I successfully establish a nationwide combat training program for a large country?
Organic chemistry Iodoform Reaction
What is the opposite of 'gravitas'?
Stereotypical names
Issues with Installing Powershell to Kali Machine
QGIS Geometry Generator Line Type
For airliners, what prevents wing strikes on landing in bad weather?
Can one define wavefronts for waves travelling on a stretched string?
Is there a problem with hiding "forgot password" until it's needed?
What would you call a finite collection of unordered objects that are not necessarily distinct?
Female=gender counterpart?
Can a malicious addon access internet history and such in chrome/firefox?
How to deal with or prevent idle in the test team?
What (else) happened July 1st 1858 in London?
Giant Toughroad SLR 2 for 200 miles in two days, will it make it?
Is it okay / does it make sense for another player to join a running game of Munchkin?
Invariance of results when scaling explanatory variables in logistic regression, is there a proof?
Proof of Lemma: Every integer can be written as a product of primes
node command while defining a coordinate in TikZ
Java - What do constructor type arguments mean when placed *before* the type?
Is it possible to build a CPA Secure encryption scheme which remains secure even when the encryption of secret key is given?
Superhero words!
Teaching indefinite integrals that require special-casing
How to be able to process a large JSON response?
2019 Community Moderator ElectionDeserialising a JSON responseJSON Reciever EndpointJson response getting truncated when getting from SalesforceExtra Backslash in Json String when exposing webserviceIllegal Value for primitive when trying to parse the json dataTrailhead : HTTP Post Issue : JSON does not contain correct case sensitive keysBest way to parse JSON Response from Google Maps?Create Salesforce Records from JSON responseJSON Parsing of REST responseto remove null value from the JSON response
We're calling an external REST service from Salesforce and are receiving a JSON response of more than 45 MB. Has anyone attempted anything like this?
json rest governorlimits
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
add a comment |
We're calling an external REST service from Salesforce and are receiving a JSON response of more than 45 MB. Has anyone attempted anything like this?
json rest governorlimits
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
Just to clarify, you are calling a Salesforce REST service from an external client or you are calling an external REST service from within Salesforce (apex)?
– Jayant Das
3 hours ago
@JayantDas I have added clarification to my question.
– Sander de Jong
3 hours ago
Thanks. Had thought that you are calling from Salesforce but good to get that clarified. Derek's answer is what I would think addresses this scenario.
– Jayant Das
3 hours ago
add a comment |
We're calling an external REST service from Salesforce and are receiving a JSON response of more than 45 MB. Has anyone attempted anything like this?
json rest governorlimits
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
We're calling an external REST service from Salesforce and are receiving a JSON response of more than 45 MB. Has anyone attempted anything like this?
json rest governorlimits
json rest governorlimits
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
edited 3 hours ago
Sander de Jong
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
asked 4 hours ago
Sander de JongSander de Jong
1,37721538
1,37721538
Just to clarify, you are calling a Salesforce REST service from an external client or you are calling an external REST service from within Salesforce (apex)?
– Jayant Das
3 hours ago
@JayantDas I have added clarification to my question.
– Sander de Jong
3 hours ago
Thanks. Had thought that you are calling from Salesforce but good to get that clarified. Derek's answer is what I would think addresses this scenario.
– Jayant Das
3 hours ago
add a comment |
Just to clarify, you are calling a Salesforce REST service from an external client or you are calling an external REST service from within Salesforce (apex)?
– Jayant Das
3 hours ago
@JayantDas I have added clarification to my question.
– Sander de Jong
3 hours ago
Thanks. Had thought that you are calling from Salesforce but good to get that clarified. Derek's answer is what I would think addresses this scenario.
– Jayant Das
3 hours ago
Just to clarify, you are calling a Salesforce REST service from an external client or you are calling an external REST service from within Salesforce (apex)?
– Jayant Das
3 hours ago
Just to clarify, you are calling a Salesforce REST service from an external client or you are calling an external REST service from within Salesforce (apex)?
– Jayant Das
3 hours ago
@JayantDas I have added clarification to my question.
– Sander de Jong
3 hours ago
@JayantDas I have added clarification to my question.
– Sander de Jong
3 hours ago
Thanks. Had thought that you are calling from Salesforce but good to get that clarified. Derek's answer is what I would think addresses this scenario.
– Jayant Das
3 hours ago
Thanks. Had thought that you are calling from Salesforce but good to get that clarified. Derek's answer is what I would think addresses this scenario.
– Jayant Das
3 hours ago
add a comment |
2 Answers
2
active
oldest
votes
There's just no way to cram that much data into Salesforce as-is.
I'd imagine you'd need to introduce a layer in the middle to break that JSON up into more manageable pieces, and also make use of async processing (probably using Queueable).
As I'm sure you know, the transaction limit on heap size is 6MB (12MB Async), and that space needs to hold the incoming response, store it again (plus overhead) when you deserialize it, and have space left over to do whatever processing you need to do.
Another option would be to have the middle layer (Heroku, some VM on some cloud provider, etc...) do the processing for you, and then create/update/delete whatever it is that you need to do via accessing Salesforce's APIs
answered 3 hours ago
Derek FDerek F
20.7k52253
I like your suggestion of having the middle layer call Salesforce's APIs. I don't know if the middle layer will be able to handle that kind of load. An alternative would be to have the middle layer implement a paging mechanism, but this would also mean more work on the Salesforce side.
– Sander de Jong
3 hours ago
I also think that doing tens of thousands of REST calls to Salesforce will not be as efficient as processing 45 times 1 MB JSON files, for example.
– Sander de Jong
3 hours ago
@SanderdeJong Depending on what precisely you're doing, you could create multiple records in Salesforce with a single request, or use the composite resource to package up multiple API calls into a single call.
– Derek F
45 mins ago
add a comment |
In Apex, no chance. The maximum response size is limited to 6/12/36MB (depending on context). You'd have to do client-side processing (e.g. Visualforce via the AJAX Proxy) in order to handle this amount of data.
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f255209%2fhow-to-be-able-to-process-a-large-json-response%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There's just no way to cram that much data into Salesforce as-is.
I'd imagine you'd need to introduce a layer in the middle to break that JSON up into more manageable pieces, and also make use of async processing (probably using Queueable).
As I'm sure you know, the transaction limit on heap size is 6MB (12MB Async), and that space needs to hold the incoming response, store it again (plus overhead) when you deserialize it, and have space left over to do whatever processing you need to do.
Another option would be to have the middle layer (Heroku, some VM on some cloud provider, etc...) do the processing for you, and then create/update/delete whatever it is that you need to do via accessing Salesforce's APIs
answered 3 hours ago
Derek FDerek F
20.7k52253
I like your suggestion of having the middle layer call Salesforce's APIs. I don't know if the middle layer will be able to handle that kind of load. An alternative would be to have the middle layer implement a paging mechanism, but this would also mean more work on the Salesforce side.
– Sander de Jong
3 hours ago
I also think that doing tens of thousands of REST calls to Salesforce will not be as efficient as processing 45 times 1 MB JSON files, for example.
– Sander de Jong
3 hours ago
@SanderdeJong Depending on what precisely you're doing, you could create multiple records in Salesforce with a single request, or use the composite resource to package up multiple API calls into a single call.
– Derek F
45 mins ago
add a comment |
There's just no way to cram that much data into Salesforce as-is.
I'd imagine you'd need to introduce a layer in the middle to break that JSON up into more manageable pieces, and also make use of async processing (probably using Queueable).
As I'm sure you know, the transaction limit on heap size is 6MB (12MB Async), and that space needs to hold the incoming response, store it again (plus overhead) when you deserialize it, and have space left over to do whatever processing you need to do.
Another option would be to have the middle layer (Heroku, some VM on some cloud provider, etc...) do the processing for you, and then create/update/delete whatever it is that you need to do via accessing Salesforce's APIs
answered 3 hours ago
Derek FDerek F
20.7k52253
I like your suggestion of having the middle layer call Salesforce's APIs. I don't know if the middle layer will be able to handle that kind of load. An alternative would be to have the middle layer implement a paging mechanism, but this would also mean more work on the Salesforce side.
– Sander de Jong
3 hours ago
I also think that doing tens of thousands of REST calls to Salesforce will not be as efficient as processing 45 times 1 MB JSON files, for example.
– Sander de Jong
3 hours ago
@SanderdeJong Depending on what precisely you're doing, you could create multiple records in Salesforce with a single request, or use the composite resource to package up multiple API calls into a single call.
– Derek F
45 mins ago
add a comment |
There's just no way to cram that much data into Salesforce as-is.
I'd imagine you'd need to introduce a layer in the middle to break that JSON up into more manageable pieces, and also make use of async processing (probably using Queueable).
As I'm sure you know, the transaction limit on heap size is 6MB (12MB Async), and that space needs to hold the incoming response, store it again (plus overhead) when you deserialize it, and have space left over to do whatever processing you need to do.
Another option would be to have the middle layer (Heroku, some VM on some cloud provider, etc...) do the processing for you, and then create/update/delete whatever it is that you need to do via accessing Salesforce's APIs
answered 3 hours ago
Derek FDerek F
20.7k52253
There's just no way to cram that much data into Salesforce as-is.
I'd imagine you'd need to introduce a layer in the middle to break that JSON up into more manageable pieces, and also make use of async processing (probably using Queueable).
As I'm sure you know, the transaction limit on heap size is 6MB (12MB Async), and that space needs to hold the incoming response, store it again (plus overhead) when you deserialize it, and have space left over to do whatever processing you need to do.
Another option would be to have the middle layer (Heroku, some VM on some cloud provider, etc...) do the processing for you, and then create/update/delete whatever it is that you need to do via accessing Salesforce's APIs
answered 3 hours ago
Derek FDerek F
20.7k52253
answered 3 hours ago
Derek FDerek F
20.7k52253
answered 3 hours ago
Derek FDerek F
20.7k52253
answered 3 hours ago
Derek FDerek F
20.7k52253
20.7k52253
I like your suggestion of having the middle layer call Salesforce's APIs. I don't know if the middle layer will be able to handle that kind of load. An alternative would be to have the middle layer implement a paging mechanism, but this would also mean more work on the Salesforce side.
– Sander de Jong
3 hours ago
I also think that doing tens of thousands of REST calls to Salesforce will not be as efficient as processing 45 times 1 MB JSON files, for example.
– Sander de Jong
3 hours ago
@SanderdeJong Depending on what precisely you're doing, you could create multiple records in Salesforce with a single request, or use the composite resource to package up multiple API calls into a single call.
– Derek F
45 mins ago
add a comment |
I like your suggestion of having the middle layer call Salesforce's APIs. I don't know if the middle layer will be able to handle that kind of load. An alternative would be to have the middle layer implement a paging mechanism, but this would also mean more work on the Salesforce side.
– Sander de Jong
3 hours ago
I also think that doing tens of thousands of REST calls to Salesforce will not be as efficient as processing 45 times 1 MB JSON files, for example.
– Sander de Jong
3 hours ago
@SanderdeJong Depending on what precisely you're doing, you could create multiple records in Salesforce with a single request, or use the composite resource to package up multiple API calls into a single call.
– Derek F
45 mins ago
I like your suggestion of having the middle layer call Salesforce's APIs. I don't know if the middle layer will be able to handle that kind of load. An alternative would be to have the middle layer implement a paging mechanism, but this would also mean more work on the Salesforce side.
– Sander de Jong
3 hours ago
I like your suggestion of having the middle layer call Salesforce's APIs. I don't know if the middle layer will be able to handle that kind of load. An alternative would be to have the middle layer implement a paging mechanism, but this would also mean more work on the Salesforce side.
– Sander de Jong
3 hours ago
I also think that doing tens of thousands of REST calls to Salesforce will not be as efficient as processing 45 times 1 MB JSON files, for example.
– Sander de Jong
3 hours ago
I also think that doing tens of thousands of REST calls to Salesforce will not be as efficient as processing 45 times 1 MB JSON files, for example.
– Sander de Jong
3 hours ago
@SanderdeJong Depending on what precisely you're doing, you could create multiple records in Salesforce with a single request, or use the composite resource to package up multiple API calls into a single call.
– Derek F
45 mins ago
@SanderdeJong Depending on what precisely you're doing, you could create multiple records in Salesforce with a single request, or use the composite resource to package up multiple API calls into a single call.
– Derek F
45 mins ago
add a comment |
In Apex, no chance. The maximum response size is limited to 6/12/36MB (depending on context). You'd have to do client-side processing (e.g. Visualforce via the AJAX Proxy) in order to handle this amount of data.
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
add a comment |
In Apex, no chance. The maximum response size is limited to 6/12/36MB (depending on context). You'd have to do client-side processing (e.g. Visualforce via the AJAX Proxy) in order to handle this amount of data.
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
add a comment |
In Apex, no chance. The maximum response size is limited to 6/12/36MB (depending on context). You'd have to do client-side processing (e.g. Visualforce via the AJAX Proxy) in order to handle this amount of data.
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
In Apex, no chance. The maximum response size is limited to 6/12/36MB (depending on context). You'd have to do client-side processing (e.g. Visualforce via the AJAX Proxy) in order to handle this amount of data.
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
answered 3 hours ago
sfdcfoxsfdcfox
261k12208452
261k12208452
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f255209%2fhow-to-be-able-to-process-a-large-json-response%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Just to clarify, you are calling a Salesforce REST service from an external client or you are calling an external REST service from within Salesforce (apex)?
– Jayant Das
3 hours ago
@JayantDas I have added clarification to my question.
– Sander de Jong
3 hours ago
Thanks. Had thought that you are calling from Salesforce but good to get that clarified. Derek's answer is what I would think addresses this scenario.
– Jayant Das
3 hours ago