Search Results

That code needs to be in a class, and then in a method. In other words, what you have is a code snippet, not a complete solution. To get started, you'd wrap the code inside a class and method: public …

for (Dom.XmlNode xmlNode : document.getRootElement() .getChildElement('recordset', null) .getChildElement('record', null).getChildElements()) { Should be: for (Dom.XmlNode xmlNode : document. …

This is true for both the XML- and JSON-based parsing options. …

The XML data is technically correct, while the UI is technically incorrect. If "default" is set, but the box isn't shown, no assignment should occur when creating/updating a lead/case record. …

You can only use getText() when you are in a valid state; therefore, you must first call next() to advance to the next event, then check and make sure that you are in a valid state (e.g. XmlTag.CHARAC …

record.field}" /> There's a parameter called "escape" that defaults to true; in other words, when you use this element, it naturally protects you from emitting characters that might be misinterpreted by an XML …

You've a typo in your XML. It should be xmlns:SOAP-ENV Instead of xmlns:SOAPENV I strongly suggest you use Dom.Document and Dom.XmlNode instead of manually piecing together strings. …

That XML is fine, though I would generally recommend you use Dom.Document to generate your XML. … Try: req.setHeader('Content-Type', 'application/xml'); …

Unlike JavaScript's Element.querySelectorAll function, XmlNode.getChildElement() and so on doesn't recursively find child elements. <UpdateResponse> isn't the immediate child of <soap:Envelope>, so yo …

According to this idea, CDATA isn't supported. It also includes a workaround you can use for now: public String stripCDATA(String str) { Pattern p = Pattern.compile('<!\\[CDATA\\[(.*?)\\]\\]>'); …

Instead of using the built-in parser directly, I'd suggest finding an XPath implementation, such as this one. Using a parser means that you have to keep track of the state yourself. You're much better …

EmailType is not a namespace, it's an attribute. The following change to your code should work. dom.XmlNode EmailsBdy = ContactBdy.addChildElement('Email', null, 'ns'); EmailsBdy.setAttribute('EmailT …

You could write your own deflate algorithm, but there's no out-of-the-box algorithm you can call upon.

The XML looks like: <Profile ...> <classAccesses> <apexClass>MyClass</apexClass> <enabled>true</enabled> </classAccesses> </Profile> You can get the values currently in production … xml version="1.0" encoding="UTF-8" standalone="yes" ? …

Omitted values will remain the same as they were before deployment. Therefore, if your permission set includes, for example, just one enabled field, then that's the only field you need in your file. T …