Error message during data synchronization: No value was entered for at least one mandatory field

Summary

The mandatory field check for data collections was implemented with edoc archive service 25.9.2.

If you have activated this option, data synchronization processes that have not passed the mandatory field check are ignored. The processes are displayed in the edoc archive service cockpit with the process status Ignored (Incomplete).

During the update process from edoc archive service to 25.9.2, a migration is normally performed in the background, which supplements the information on the mandatory fields in the field mappings of the process types.

This migration is faulty in build 25.9.2: the mandatory field violations are not recognized and the ECM system returns an error when archiving.

No value was entered for at least one mandatory field.

The bug has been fixed in this build: 25.10.1

To solve the problem, we provide you with two solutions for different scenarios:

• Scenario 1: You have only configured a few field mappings that you can easily edit manually.

• Scenario 2: You have configured numerous field mappings, making manual editing of the field mappings time-consuming.

If you have already updated to edoc archive service 25.9.2, you can use one of the following solutions to fix the error.

Important requirements

Prerequisites for solution 1:

• Access to the administration of edoc archive service (browser).

Prerequisites for solution 2:

• SSH access to edoc platform with edoc archive service with permission for MicroK8s.

• edoc archive service version 25.10.1 (with bugfix).

Solution

Select the appropriate solution depending on the scenario.

Solution 1: Re-save field mappings of the affected process types

This solution is well suited for scenario 1, where you only need to save some field mappings manually.

1. Open the administration of edoc archive service in your browser.

2. Navigate to Map systems and process types > Configure process types.

3. Navigate to Configure field mapping for each process type concerned and click Save again.

Solution 2: Performing the migration again in the edoc archive service container

This solution is well suited for scenario 2, where you have numerous field mappings that you can update with the migration of the edoc archive service container without manually editing the field mappings.

1. Establish an SSH connection to edoc platform with edoc archive service.

2. Execute the migration in the edoc archive service container again with the following command:

   Bash

   kubectl exec -it -n <namespace> archive-service-deploy-<podId> -- php artisan app:add-is-required-and-name-to-every-field-mapping
   

For the namespace variable, insert master, staging or test according to the namespace. You can add the podId variable using the tab key.

You can also determine the pod name from the list that you display with the following command before entering the command:

kubectl get pods -A