New answers tagged

-1

One of the methods to send it would be converting into base64 format and sending the encoded value as a string.


3

There are several & characters in the string, so they are being parsed as separate parameters. If you can't change the way the external app encodes the string, you'll have to get the separate parameters and rebuild the string. String report = RestContext.request.params.get('report'); String param1 = RestContext.request.params.get('_nc_oc'); String ...


0

You are getting the full string. The only issue is when you debug it there is a limit on printed characters per debug statement which is likely truncating the output. Hope this helps.


-1

This is 3 years late, but if anyone ever sees this, you can also use responseString = response.getBody() and make a string of the response, then use responseString.Replace('"reservedWord":', '"yourNewWord":') to map response fields to a wrapper class.


1

You declare demoGoods locally, then you assign it and return it. But you never touch the RestContext.response in order to set it there. Your test expects you to do so. DemoGoods = Database.query(qryString); // here you need to set RestContext.response.responseBody return DemoGoods; Most likely, you will just serialize your records. RestContext.response....


0

I have the same issue, that is quite bad. I found something here but it's not the best. https://developer.salesforce.com/forums/?id=9060G000000UUe2QAG


Top 50 recent answers are included