Commcare-export

Latest version: v1.13.0

Safety actively analyzes 681866 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 12

1.7.1

190 switch from `jsonpath-rw` to `jsonpath-ng`

1.7.0

* 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

* https://github.com/dimagi/commcare-export/pull/187: Fix 'KeyError' for `messaging-events` API

1.6.1

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

1.6.0

**Enhancements**
175 - support saving JSON data to Postgres databases. [Practical details here](https://confluence.dimagi.com/display/commcarepublic/CommCare+Export+Advanced+Features#CommCareExportAdvancedFeatures-SavingdataasJSON)
179 - add ability to export messaging events

1.5.0

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

Page 3 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.