With version 1.11.1, the configuration for Germany was structurally aligned with the other country configurations.
The requirement to define separate storage areas for taxonomy (DSFinV-K) data and document data has been removed and replaced with the 'Cloud Archive' check box, which is also present in the other country configurations.
Adjustment for older clients
As a result of this change, systems in Germany that were originally initialised with a version < 1.11.1 may experience problems with data transfer if a configuration update has been carried out without upgrading the client version to a version > 1.11.1 first.
When the configuration is updated, the new property ("CloudArchive": true) is incorporated into the configuration, whilst the old properties defining the storage areas are deleted. As clients running versions prior to 1.11.1 cannot process the new property, this results in Taxonomy (DSFinV-K) data not being stored in the cloud archive.
The system is NOT affected in the following scenarios:
- The client has been updated to a new version (> 1.11.1),
- Following the client version update, the configuration was changed to the new settings and updated (PUT /api/v1/management/clients/byCloud/{clientId}), OR
- The client is still running with the old configuration (WITHOUT updating the configuration)
- The client is still running on a version < 1.11.1 (generally not recommended),
- The configuration has never been updated.
If you find that DSFinV-K data is missing from one of your systems, the system may be affected.
To resolve the issue, please proceed as follows:
- Ensure that the 'Cloud Archive' checkbox is ticked in the configuration.
- Update the RetailForce Middleware to the latest version – ideally.
- Contact us (via a support ticket or by email to your contact person) so that we can temporarily enable the following function for you.
- Once we have confirmed that the function has been enabled,
- call the endpoint POST /api/v1/cloudsync/{clientId}/startSendingToCloud.
This function checks if data which is stored locally (client data) is missing in the cloud archive and uploads it.
Note: only call the endpoint POST /api/v1/cloudsync/{clientId}/startSendingToCloud once and not multiple times. The upload might take a while, depending on the data missing in the cloud archive.
Note: POST /api/v1/cloudsync/{clientId}/startSendingToCloud can only be executed after activation by RetailForce! Calling this endpoint without activation will return an error.
Comments
0 comments
Please sign in to leave a comment.