You can’t update the following columns when syncing updates to Salesforce: You can’t set the following columns when syncing writes of new records to Salesforce:
These correspond to the system fields found on most Salesforce objects. Heroku Connect ignores writes to some columns that are read-only when syncing writes to Salesforce. While you can read from the columns to aid in debugging you must not write to these columns as you will likely cause errors with Heroku Connect sync operations. These columns are used by Heroku Connect to track and report on sync operations and must not be removed from the table. If the last sync operation resulted in an error then this column will contain a JSON object containing more information about the error Indicates the last sync operation performed on the record Only created when the Salesforce object has an IsDeleted field. Used to track the IsDeleted field from Salesforce, allowing Heroku Connect to process records deleted in Salesforce when polling for updates.
The date and time (in the UTC time zone) that the Salesforce object was last modified and used by Heroku Connect when polling for updates The Salesforce object Id field that is automatically populated when records are synchronized with Salesforce Heroku Connect makes no guarantees about when the sequence is reset or about the uniqueness of values across reloads. This should be considered an implementation detail. In addition to the Salesforce fields you choose to map to database columns, Heroku Connect will automatically add the following system columns to the mapped tables: Column nameĪ unique, auto-incrementing integer primary key. If you’re using an ORM framework, ensure that it doesn’t attempt to create the underlying tables in the database. If the table isn’t created correctly, you experience errors when syncing data. Heroku Connect doesn’t replace an existing table when creating a new mapping.