In my opinion we may have divergences in BO designer during the cardinalities check when:
clang='EN'
, the error is :"cardinality is not valid" because i forced 1 by N relationship and BO checks and see N by N relationship due to the lack of the language.
We have multilanguage selection during the query. This table has two primary keys, the code and the language. For this, bo thinks there are two rows for each N row in another table, so it thinks you have a N by N relationship. We don't select the code at this point because the user will select when creating the query:
*the part circled was introduced by me after the checking. if I hit detect button it says ok.clang='EN'
, the error is :"cardinality is not valid" because i forced 1 by N relationship and BO checks and see N by N relationship due to the lack of the language.
