Thanks for your support of Codebook and posting the disucssion forum, although I’m sorry to hear about the issue you’re experiencing.
First, a bit of background on the issue I believe is causing this: Codebook tracks changes that are made to your database along a high water mark for each replica database that you synchronize with. An issue has been identified and addressed that could cause the high water mark tracking to create a gap in sequence, thus “ignoring” changes that may have occurred during a synchronization between two Codebook instances. This issue only affected a small subset of Codebook users. We believe that your instances of Codebook are likely affected by this issue. Again, this issue has been already addressed.
There are two possible approaches for resolving this specific conflict going forward:
Merge data by manual entry:
One option is to select a single instance of Codebook to operate on, making that instance your central copy during the mergring process. This will require you to review the data on each other install of Codebook and recreate the missing entries/data. Once this single instance of Codebook contains all the correct data, you’ll want to replaces= the other instance’s data with the central copy’s (by either performing an overwrite or restore depending on which platform you used as the central copy).
If you typically use one platform to enter most of your data on, I would recommend making this the central copy as it should require the fewest additions.
Merge datra by export to CSV
Another option is to utilize the CSV export option included with Codebook on the desktop. You will need to export each instance of Codebook to separate CSV files, then create a single merged CSV file representing all data elements across your Codebook instances. Once all data is located in a single CSV file, we can prepare Codebook for the import.
I’ll be happy to provide further details on either of these options.
You mentioned Codebook for iOS and Codebook for macOS, how many devices are you using Codebook on?
Again, I’m very sorry for this difficulty. We try very hard to make sure we have fully tested and verified behavior of the application prior to releasing it the public. We have utilized this synchronization system within Codebook for many years successfully, yet we appologize for the defect you were affected by.
Please let me know which option you’d like to proceed with, and if you have any further questions. Thanks!