Improve behavior when using multi-tenancy in ORM but not in the backend

Description

See https://stackoverflow.com/q/66303479/6692043

I'm thinking we should at the very least have a more useful error message, where we explain which property must be set.

Maybe, just maybe, we could also enable multi-tenancy automatically in the backend if the mapper tells us it needs multi-tenancy?

Activity

Show:
Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Priority

Created February 22, 2021 at 9:12 AM
Updated September 10, 2021 at 7:24 AM
Resolved May 6, 2021 at 2:53 PM