Why would I want record updates?
There are many different types of data sources you might use where records can be updated after they have been created. For example:
Some surveys may be submitted when partially completed and then resubmitted when updated later
Online reviews and app reviews can often be edited after they have been posted
Your data warehouse may have had new demographic data joined to existing customer feedback records
In all of these cases, by specifying a unique ID, Kapiche is able to detect if the record already exists in a project and update its data. This means that you would be able to re-upload the updated data or have it automatically ingested via an integration for the most up-to-date representation in Kapiche.
Selecting a unique ID
Kapiche allows you to specify unique ID fields when defining the Schema on Project creation.
If your data doesn't contain a unique ID field you could combine multiple different fields to produce a unique combination (e.g. with Survey data you can combine Survey ID and Respondent ID together to provide you with a reliable unique ID).
Checking a project's unique ID
When visiting the settings page for a project, you can expand the unique ID fields section to see which columns (if any) are being used to form a unique ID.
Note: The unique ID needs to be set when the Project is first created as it cannot be changed later.
If you have any questions about configuring Record Updates (or anything else!) you can get in touch with us any time by hitting the blue chat button to your right 👉