Push

Push writes sanda's numbers into fields on your Salesforce records: revenue over the last twelve months on each Account, the overdue balance beside it, the date of the last order. The numbers come from your semantic fluid, so they mean what your team agreed they mean. They land in ordinary Salesforce fields, so Salesforce reports, list views, flows and page layouts read them like any other field.

Push is included on Standard and Enterprise, and during a trial. You find it in the console under Activate · Push, once it is switched on for your console. Until then the console doesn't list it: it isn't in the navigation, and Settings · Plan & budget doesn't name it among your edition's features.

How it works

your semantic fluid: a number per record, such as revenue or overdue balance
        |  read on each run, one row per Salesforce record
        v
compared with what Salesforce last accepted from sanda
        |  only the records whose values changed
        v
the fields on those records in your Salesforce org

1. You connect a Salesforce org by signing in to Salesforce as the user sanda writes as. See connect Salesforce.
2. You define a push: the Salesforce object, the field that finds each record, and the sanda value written into each field. You preview what it would send before anything goes. See create a push.
3. It runs after a connection syncs, on a schedule, or when you press Run now. Each run reads the values, formats them the way Salesforce stores them, and compares them with what Salesforce last accepted. Only the records whose values changed are sent, and a run where nothing changed makes no call to Salesforce at all. See runs and refusals.

This is not the Salesforce connection under Data · Connections, which reads your Salesforce data into sanda (see Salesforce). Push goes the other way, and it is set up separately. The two work well together: the Salesforce sync lands each record's Id in your warehouse, and a push uses it to find the record again.

What counts as a change

A record has changed when what sanda would send for it has changed: the exact values, formatted for their fields. A sync running, or a warehouse row being touched, is not a change on its own.

• A number is rounded to the field's decimal places before it is compared, so 100.004 and 100.0049 sent to a two-decimal currency field are the same value.
• An empty value clears the field. A metric with nothing to measure doesn't leave last month's number standing.
• A Salesforce Id is compared in its 18-character form, so a record that arrives once with a 15-character Id and once with an 18-character Id is one record, sent once.

sanda records a value as sent only when Salesforce says it accepted it. A run that stops part way leaves nothing half recorded: the next run sends whatever Salesforce did not confirm.

Editions and limits

One push reads at most 50,000 records and writes at most 100 fields. A push that reads more refuses to run and says so: narrow it with a condition, or split it into pushes by region or segment.

If your workspace moves to an edition with fewer pushes, it keeps every push. Its oldest pushes keep running, up to the new edition's count, and the rest keep their definitions and wait. On Basic none of them runs. Moving back up is immediate. See editions.

What Push never does

• Delete a Salesforce record.
• Create a record when it finds records by their Id.
• Clear a field because a record has left the push. A record that no longer matches a push's conditions stops being sent to, and keeps the value it has.
• Send a value Salesforce already has.
• Spend the last 10% of your org's daily API allowance. See your API allowance.
• Record a value as sent that Salesforce did not confirm.

Who can do what

A push writes into Salesforce on the whole workspace's behalf and spends your org's API allowance, so only owners and admins change one. A preview reads your warehouse and sends nothing, so anyone who can open the console can ask for one.