You have uploaded at some point protocol data to a run but haven’t imported data to all readout definitions.
Alternatively, you might have created a new readout definition in your protocol after you already have imported data into runs.
In either case, you want to complement existing runs with the missing/new data.
Just like compound batch level data, you cannot overwrite existing data in your readout definitions via the file (bulk) import. To change ("overwrite") existing values, you would have to manually edit the data fields within your vault; for bulk import though, you can complement missing data.
Important to remember when complementing missing values in bulk are the two possibilities to add data to a run:
Start out by importing your data file to the project the run belongs to. Keep the initially offered radio button selection of “Add Readouts (protocol data) only”.
Possibility 1: You want to add the missing readout definition and make these addition obvious when looking at the data in your table. The result would look something this, with the new readout in a separate row (Run view):
To obtain this, map your IDs as usual, select the existing Run (Date) and map only the missing data column!
Possibility 2(a): You want the new data integrated seamlessly, displaying only one row in the search view:
For this, have all the original data including the new column available and upload it. Now map everything (the missing data as well as all the previous data), and continue your import.
In both cases, you will receive during step 3 of the import a notification that the Run will be updated.
Possibility 2(b): There is another option, to seamlessly integrate the data: delete the runs entirely and re-import them again. See here on how to delete a run. If you registered with plates, you can, but don't have to delete those imported plates. In other words, this is optional and you save yourself some steps by not deleting them. See here on how to delete a plate.