New answers tagged

0

Since ownership changes can cause expensive recalculations, this restriction keeps that calculation down to a reasonable time frame. You will need to break up your updates such that the constraint is observed. In other words, reach set of records must belong to the same user and be transferred to the same new owner.


0

Suggestion, trim it down - A lot of the stuff in your query from the docs is "optional" and you can get rid of a lot of clutter in the soap header. Here is what I use as a starting point when trying the same operation, as you can see the header is a lot shorter, while the CreateRequest is pretty much the same as yours : <soap:Envelope xmlns:soap=...


0

Field: SecuritySettings Body: <?xml version="1.0" encoding="utf-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tns="http://soap.sforce.com/2006/04/metadata"> <soapenv:Header> <tns:SessionHeader> <tns:sessionId>token</tns:sessionId&...


1

Here's what worked for me: <?xml version="1.0" encoding="UTF-8"?> <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <s:Header&...


1

You shouldn't be specifying the the ObjectID. Here's the upsert I use in Postman: <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <s:Header> ...


1

If no changes are made for the Profile's Password Policies, then there's no ProfilePasswordPolicy for it. Represents a profile’s password policies. Profile password policies override org-wide password policies for that profile’s users Checking in the UI, you'll see what is displayed is identical to the Organization's Password Policies. SecuritySettings has ...


2

Unfortunately, there does not seem to be a way to control this according to Salesforce https://help.salesforce.com/s/articleView?id=000331375&type=1


0

You can simplify you repeat call much further. In the repeat <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Header> <fueloauth xmlns="http://exacttarget.com"> auth_token </fueloauth> </Header> <Body> ...


Top 50 recent answers are included