Versions Compared

Old Version 3

changes.mady.by.user Matt Dougherty

Saved on

compared with

New Version Current

changes.mady.by.user Steven Cooper

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • This element of the Streaming API documentation should be reviewed.

  • The id in the data event will persist for each update that comes through for that record.

  • The checksum will be unique for each update to a data event id

  • The client should have logic to check if the id was previously processed. If so, then you have an update to that data event coming through. The client should write the values for the most recent checksum for a given id to their database. The most recent can be determined by the created_at in the data event payload.

  • This is most commonly seen with Summary records as they are updated throughout the entire day, but can be seen with other data types. It is expected behavior to see updates for records days after the day of. This is due to user behavior that can be explained in this doc for cloud and this doc for SDK.

What happens if we create 2 main streams for the same org?

...