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?

Environment

None

Assignee

Unassigned

Reporter

Yoann Rodière

Labels

None

Suitable for new contributors

None

Pull Request

None

Feedback Requested

None

Fix versions

Priority

Major