I'm upgrading from v2.6 to v3.5 and i'm getting an error that didn't occur on v2.6

I have this M2M relation:

Roles.ID <- RolesTablePrefixes.RoleID TablePrefixes.ID <- RolesTablePrefixes.TablePrefixID

And right after I do a "Reverse-engineer Tables to Entity Definitions" I get this error:

"The entity 'UsersRole' is mapped onto the target 'myDatabase.UserRoles' however 'UsersRole' doesn't have any identifying fields set, while the target is a table. When an entity is mapped onto a table, it requires at least one identifying field."

I have my PK/FK relationships set on the database, what else do I need to do to fix this error?

the intermediate table userrole does have a PK defined? If so, do you have the preference IdentifyingFieldsFollowDBPrimaryKeyConstraints set to false? If so, is the equivalent in project settings also false or default? Then that's the reason. You can also manually set the PK of the entity btw, simply select the fields in the project explorer and right-click to mark them as identifying fields.

Fixed. Thanks Otis