Skip to content

Salesforce

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade B · dataset: API (the vendor’s response payloads) · type salesforce

What it is

A Salesforce org. In the test estate it is the service cloud: customer accounts and the cases raised against shipments and claims. The connector reference is Enterprise SaaS and ERP.

Grade

B. The download holds the model. The platform itself needs a vendor account or trial. A free Developer Edition org is enough.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typesalesforce
Settingslogin_url, username, client_id
Credentialspassword, security_token, client_secret

The test connection

Quillmere service cloud

SettingTest value
login_urlhttps://login.quillmere-sf.invalid
usernameface-integration@quillmere.invalid
client_iddemo-connected-app

Credentials: password, security_token, client_secret. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download salesforce.zip and unzip it. It holds SOQL query responses for Account and Case, and expected.json.
  2. For a live org, sign up for a free Developer Edition and create the Account and Case records the responses hold.
  3. Add the connection with the settings above, pointed at your org’s login URL.

What FACE finds

Against a real org, FACE reads /sobjects and /sobjects/{X}/describe. The dataset is SOQL query responses.

DatasetKindDomainPrimary keyRowsFields
AccountsobjectcustomersId66
CasesobjectclaimsId1010

Declared foreign keys:

  • Case (AccountId) references Account (Id)

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 3 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
claimCase.Claim_Number__cfiles, guidewire, sharepoint
customerAccount.Customer_Number__cfiles, hubspot, kafka, oms, postgres, redshift, sap, snowflake
shipmentCase.Shipment_Number__cbigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, sap, servicenow, sharepoint, tms, whs, yms

Evidence it holds for the planted anomalies:

  • ANOM-2, A claim near its filing deadline. salesforce/query_Case.json in salesforce.zip, look for "Claim_Number__c": "CLM-2026-0101" (escalated case).

See all connectors at once for the walkthrough across every source.

Download

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • salesforce/query_Account.json
  • salesforce/query_Case.json
  • salesforce/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.