**Upgrade notes**
If you are exporting to SQL and using config files with multiple tables (Excel sheets) it is recommended that you do a full re-export of your data to ensure that there is no missing data. You could do this in one of the following ways:
1. Use the `--start-over` flag to ignore any existing checkpoints.
2. Edit the file to change the checkpoint key.
3. Change the checkpoint key manually using the `commcare-export-utils set-checkpoint-key` command.
**New features**
(https://github.com/dimagi/commcare-export/pull/123) add `sha1` function to allow creating hashes of output values. Mostly useful when exporting nested objects and the jsonpath ID becomes too long for the SQL primary key column.
**Improvements / fixes**
(https://github.com/dimagi/commcare-export/pull/118) Don't set checkpoint to current time. Always use time from batch if available, otherwise don't log a checkpoint.
(https://github.com/dimagi/commcare-export/pull/121) Use a separate checkpoint for each table being exported. This impacts any export configurations that have multiple tables configured in one file. Fixes https://github.com/dimagi/commcare-export/issues/119
**Other Changes**
* improvements to console logging
* fix deprecation warnings