Because of how censor revisions works in combination with the table temporary IDs, only a project's privileged users can upload table data. Not sure if this counts as a bug, or we'll just have to give all the data scientists the privileged flag (might be super difficult to work around).
Because the censor uses the revision's IDs to check for restricted access, but a table revision only has temporary IDs, the query breaks and dies. The workaround is to make sure the user is a privileged user that can see and edit restricted records.
Because of how censor revisions works in combination with the table temporary IDs, only a project's privileged users can upload table data. Not sure if this counts as a bug, or we'll just have to give all the data scientists the privileged flag (might be super difficult to work around).
You get this error thrown (relevant parts):
Because the censor uses the revision's IDs to check for restricted access, but a table revision only has temporary IDs, the query breaks and dies. The workaround is to make sure the user is a privileged user that can see and edit restricted records.