Distinguishing a complete backup from a record export

A complete backup serves to back up the current working state of DiPAgE as completely as possible. Besides finished plant protection product records, this can also include partial data and other working information. Exporting individual protocols, by contrast, serves mainly to file specific plant protection product records permanently, to pass them on, or to import them again on another device.

For the ongoing archiving of finished records, the protocol export is particularly suitable. A complete backup is additionally worthwhile if the complete working state of the application is to be preserved or transferred.

Creating a complete backup

In the “Profile” or “Data management” area, a complete backup of the current DiPAgE working state can be downloaded. This backup file should be stored in a reliable place, for example in the farm’s file storage, on an external storage medium or in a cloud storage approved by the farm.

A backup file is especially valuable if a device has to be replaced or the local browser state is lost. It complements the export of finished protocols, but does not necessarily replace orderly archiving of the individual plant protection product records.

Restoring a complete backup

A complete backup can be restored in DiPAgE in order to recover an earlier working state or to transfer a complete working state to another device. Note that restoring a complete backup replaces the existing working state on the target device.

Before restoring a backup on a device that is already in use, the current working state there should therefore be backed up first as well. That way you can return to that state if in doubt.

Importing individual plant protection product records

In the “Protocols” area, exported plant protection product records can be read in again. The machine-readable file formats provided by DiPAgE are supported, in particular JSON, XML and CSV; bundled files can also be imported, depending on the export form.

The import is suitable, for example, for transferring records between two devices, for taking over records from a shared file storage, or for checking records provided by another person.

Incomplete records during import

If an imported record does not contain all required details, DiPAgE can point out the missing information. Such records can be accepted for further editing and marked as incomplete. The missing mandatory details must be added before a legally compliant export.

DiPAgE can thus also serve as a checking and post-processing environment for data that was not created completely in the application itself.

What happens in the event of conflicts?

If, during import, a record meets an existing record with the same identity but different content, DiPAgE shows a conflict resolution window. The local and the imported version are shown side by side there. Differing properties are highlighted, so that you can see where the two versions differ.

You can then decide which version is to be kept. This avoids a differing file overwriting an existing record unnoticed. For larger imports, conflicts should be checked deliberately and only then saved.