Reassuring that it isn’t a problem with our configuration or my mapping, but also a bit frustrating because this means that both parts of dealing with the problem I mentioned in my prior post (both Deleting collectionobjectattachment via api endpoints and creating thousands of new attachments) are blocked until these errors get fixed in the next version. Since I can’t use batch edit to change ‘id’, I also can’t work around it by just changing the table that the existing attachments are attached to.
Is there a decent way to do this by directly manipulating the SQL? Would appreciate assistance in getting this done soon, as it is blocking me uploading a bunch of other new data into the CO attachment table.