It's not clear under what conditions this happens yet, except we know that disabling strict mode works. So I suspect that one of the null values introduced by strict mode leads to the situation where Magma thinks there is a temporary ID somewhere? Or perhaps trying to set "empty" on a parent model causes the above? Need to investigate.
May be related to #202, but it seems like updating certain types of attributes with
null
leads to an issue with temporary IDs.When updating a bunch of clinical data via the etna gem, using strict mode leads to a Magma error:
It's not clear under what conditions this happens yet, except we know that disabling strict mode works. So I suspect that one of the
null
values introduced by strict mode leads to the situation where Magma thinks there is a temporary ID somewhere? Or perhaps trying to set "empty" on a parent model causes the above? Need to investigate.