small bug: record needs to exists already in destination project

[ThomasVermes]

Dear all,
here below I copy my redcap post which might be lost =)
https://redcap.vanderbilt.edu/community/post.php?id=223840

I've tested it a bit and here below some comments:

• small bug: with "Auto-incremented Destination ID" selected a first record needs to already exist in the destination project.
  

This is more or less explained in the "migration note":

Error creating record in DESTINATION project 125 - ask administrator to review logs: The record id field (record_id) is missing.
But I had not activated them immediately and from the logging page it was not possible to identify the problem.

• feature request (1): Enable checkbox. As other EMs do, it would be nice to be able to enable or not the migration at "List of Destination Projects to receive Mirrored Data:" level. In this way we can configure the module and save the changes without having them immediately in production.

• feature request (2): It would be nice to have the opportunity to choose another "matching" field other than the record_id in destination project.

With
would be nice to select a field from source project with has to match with an (unique) field in the destination project. (I requested the same also for the "Copy Data On Save" module, see here for the discussion --> lsgs/redcap-copy-data-on-save#8 )

best

Thomas

REDCap 14.1.4 · PHP 7.4.20 (Windows OS) · MySQL 8.0.11

[ThomasVermes]

small bug: with "Auto-incremented Destination ID" selected a first record needs to already exist in the destination project.
-->The first record cannot be 0.
--> If the first record is "-1" the incrementation function work and create a record "0", but the next one will not create the record 1 but give the following error:

Error creating record in TARGET project. Target ID, 0, already exists in Destination project 2117 and clobber is set to false ().