Figured it out, finally! The following returns all records that fit the MatchingRule.
To authenticate, use login()
Also, this trailhead will help you get started with SOAPUI (similar to Postman), which is where I did all the following requests from.
You can perform a SOQL query on the account object using the SOAP API.
To get the records using the External Id field, use the query like below.
SELECT Name FROM Account WHERE ExternalId = 'value'
If you need the fuzzy search you can do it using the below query.
SELECT Name FROM Account WHERE ExternalId LIKE '%value%'
In a similar way, you search for other ...
The issue here is that the authenticated user does not have CRUD access to the object. The WSDL can contain a reference to the object even if the actual connected user does not have permission to see it.
This is likely an API version error. This field was introduced in API v24.0. Using an older version of the API, you won't be able to see this field (query, insert, update, etc). You need to upgrade your API version on the other system.
The alternative way to change the ClientBase Endpoint is to directly reassign the Endpoint.
SoapClient client = new SoapClient(binding, addressSoap);
SalesforcePartner.LoginResult loginResult = await partnerApi.loginAsync("email@example.com", "password" + "securityToken");
client.Endpoint.Address = new EndpointAddress(...
As @RafalWolsztyniak stated, SFMC SSJS currently uses ECMAscript 3, so a good portion of these types of functions or methods you have been able to use for years in JS are not available in SSJS. BUT, this does not mean we lose the abilities of these functions, just that they are not premade or 'baked-in' to SSJS.
For instance, if you create the backfill like ...
The Core library currently stands at version 1.1.1 and supports
ECMAscript 3.0. This version represents the current, original version
As such newer functions functions than ca. 2000 are not ...
SoapFaultException extends ConnectionException which extends Exception.
That means default Exception (Throwable) methods are available with SoapFaultException like getCause(), getMessage(), and getStackTrace().
Try calling those instead, specifically getMessage() which returns the message passed to the Exception constructor:
public static Object querySf(...