I am not getting any "Via" properties, e.g. Role.PermissionCollectionViaRolePermission.

Do I have to create them manually now?

Added it manually.

On another note, if I change the name pattern for rel. properties is there some way to apply those changes to the entities I have already added? This is sorely needed.

Where is the option to stop it stripping the letter "s" from entity names (properties too?). I've got an entity called Statu. And various relationship properties called "Statu".

I disabled the plugin event thing to stop the singular-ness.

I am not getting any "Via" properties, e.g. Role.PermissionCollectionViaRolePermission.

Do I have to create them manually now?

In the Project Properties, please set AutoAddManyToManyRelationships to true (default is false).

In general, you shouldn't add them automatically, as you'd get many unwanted m:n relationships as well, so add the ones you want manually.

Yeh in hindsight, I like that it doesn't auto add them.

I am still wondering if there is a way to apply changes in settings to already imported entities. Currently, if i change something (like a name pattern) I am having to remove all the entities and re add them which also has me recreating M2M relationships and any other customisations. Its not a huge deal, but sometime I go ahead and start customising my entities adn then realise I forgot to set the name patterns. Then i sigh and do it all over again.

I would suggest these make better defaults:

OneManytoOne - {$EndEntityName}Using{$StartEntityFieldNames}

and

OneToMany - {$EndEntityName}Using{$EndEntityFieldNames}

Beats ending up with "User", "User", "User_" which lacks meaning.

Hi Sam,

Unfortunately, not everybody wants that change in settings populate changes all over project objects. Neither a fixed manner to name m:n relations. If you want to apply some setting to existing entities you can create a plugin for that.