Skip to content

Releases: dimagi/commcare-export

1.7.3

15 Jul 14:23
ca29be5
Compare
Choose a tag to compare

#192: Add unique function for removing duplicates for list output

1.7.2

07 Jul 14:31
6043909
Compare
Choose a tag to compare

#191: use 'date_last_activity' for filtering / ordering of messaging data

1.7.1

30 Jun 09:58
0538bad
Compare
Choose a tag to compare

#190 switch from jsonpath-rw to jsonpath-ng

1.7.0

30 Jun 09:49
a06e219
Compare
Choose a tag to compare
  • #189 Add option to export root document if no sub-document exists
    • This option can be invoked via the --export-root-if-no-subdocument command line argument
    • When the root document expression of an export refers to a sub-document or list of sub-documents the all source expressions will be evaluated against the sub-document unless prefixed with $. in which case they refer to the root document. In cases where it is desirable to have a row exported even if the sub-document does not exist the --export-root-if-no-subdocument can be used. When this happens only root document expressions (prefixed with $.) will be evaluated. All other expressions will yield a blank value.

1.6.2

22 Jun 14:10
5b6030c
Compare
Choose a tag to compare
  • #187: Fix 'KeyError' for messaging-events API

1.6.1

17 Jun 07:50
89e087e
Compare
Choose a tag to compare

Enhancements
#186 - more verbose error logging when --verbose flag is used
#184 - update messaging events pagination parameters to support API update

v1.6.0

16 Mar 11:55
888f144
Compare
Choose a tag to compare

Enhancements
#175 - support saving JSON data to Postgres databases. Practical details here
#179 - add ability to export messaging events

v1.5.0

02 Feb 08:07
9f82c71
Compare
Choose a tag to compare

Major changes

Change in pagination mode (#159)

This change only applies to form and case exports to all supported SQL databases. It does not apply to exports of other data types or other output formats.

This release introduces a new pagination mode for the tool in order to avoid certain edge cases where data may be missed in the requests to the CommCare API. Previous versions used the modification dates of forms and cases for sorting and pagination ("server_modified_on" for forms and "server_date_modified" for cases). From this version onward the default will be to use the "indexed_on" field for sorting and pagination.

The new pagination mode will automatically be used in the following circumstances:

  • All new tables (ones that do not have an existing checkpoint)
  • Any runs of the command that use the '--since' command line parameter
  • Any runs of the command that use the '--start-over' command line parameter

The old pagination mode will continue to be used for existing tables as long as none of the statements above apply.

It is recommended that ALL existing tables be re-synced using the new pagination mode. This can be done by passing '--start-over' on the command line for the first run of the tool. Once the tool has completed at least one checkpoint it will continue to use the new pagination mode for that table from that point onward.

Any tables that continue to use the old pagination mode will output a warning at the start of the command:

2021-01-27 14:19:43,302 commcare_export.cli WARNING 
====================================
This export is using a deprecated pagination mode which will be removed in future versions.
To switch to the new mode you must re-sync your data using `--start-over`.
See https://wiki.commcarehq.org/display/commcarepublic/CommCare+Export+Tool+Release+Notes for more details.
====================================

Minor changes

Enhancements

#173 - add "data source" and "last_doc_id" to checkpoints
#171 - test that emitted rows is a generator

v.1.4.0

11 Dec 16:13
5f54ab9
Compare
Choose a tag to compare

This release fixes a major issue with exporting to SQL databases and includes a few new functions and improvements.

Bugfixes
#170 - fix data not writing until the end of the last batch (introduced in v1.3.0)

This bug may have resulted in data not being written to the SQL database. If an error occurred while writing data to the SQL database any data which had already been read into memory would not be written to the database but the checkpoint would still point to the end of the batch.

Enhancements
#169 - use nvarchar with fixed length in MSSQL to allow indexing
#162 - remove whitespace from beginning and end of column names
#157 - support for python 3.8

New features
#167 - add form_url and case_url Map Via functions
#158 - add format-uuid function to format UUID hashes

1.3.3

26 Jun 08:18
6e75d5b
Compare
Choose a tag to compare

Fixes a bug where you would get an error after exporting 11 batches of data.

Improves data type support