Call Purposes

This table has 1 row per call purpose per org.

ColumnTypeDefinitionSample Value(s)Sample Use
BENTOVarcharA collection of machines that power the Outreach app. Orgs live inside these.This may distinguish orgs that are in different data centers.
CREATED_ATTimestamp_NTZThe UTC datetime that the call disposition was created in Outreach.
DML_ATTimestamp_NTZA datetime (local to server) in which the row was last modified. dml_at can be used to identify updated and new records, but as tables may not see changed records every day, it is not authoritative on when the table was last synced. 2019-01-01 12:14:01:10Where dml_at::date >= current_date-7 This will return all rows modified in the last 7 days.
DML_TYPEVarcharThe type of manipulation that last occurred to a row.'update', 'delete', 'insert', 'backfill', 'backfill-delete'Where dml_type <> 'delete' Excludes deleted rows.
IDVarcharRepresents an individual row of data in a table. Fields in other tables that match to this ID will be called thisTable_id. e.g. ID in the calls table will appear as the call_id in another table.Count(1), count(id), and count(distinct id) are equivalent in a table without joins or groupings for a given bento & o_id.
IS_DELETED_IN_APPBooleanIs the latest dml_type "delete" or "backfill-delete".Where is_deleted_in_app = false Only keeps undeleted rows.
NAMEVarcharThe name of a purpose, typically with business context.
ORDERNumberThis is the order that the call purposes will be listed in the app.
O_IDVarcharOrganization ID, also called instance ID. This is the ID for your unique Outreach account.Most commonly used on joins alongside other primary keys. where a.o_id = b.o_id and a.id = b.a_id
SURROGATE_IDVarcharAn md5 hash of bento, o_id and ID for a table.This can be used to get distinct counts of records if an account has more than 1 org instance. Two orgs will both have a prospect with ID of "1" but each will have a different surrogate ID.
UPDATED_ATTimestamp_NTZThe UTC datetime for the last time this record was updated.2019-01-01 20:14:01:10Almost equivalent to dml_at (but adjusted for time zones), but doesn't include record creation or deletion.