Activities of "BradAdler"

@yekalkan hi. The question won't work for me as:

1. It uses coding when I am trying to work with the ABP suite
2. It is a many-to-many relationship and need 1-to-many.

I am going to try and replicate the problem using a simple project much like I did above (see 3 Sep 2022).

@yekalkan hi.No the goal was not achieved. The simple example I tested worked, as described above. The more complex solution that we trying to build did not work per the original post.

@ykalkan hi. Thanks for the suggestions.

Regarding:

1. Collection names filed doesn't exist in v5.3.3.: The screen shot clearly shows the Collection Names field in the **Advanced **tab of the Define a navigation property.
2. I guess you need to type Users in Collection name filed.: I tried this and Save/Generate failed too.

I have included another screen shot showing how the Collection Names lookup only displays the App{tables} when I expect it to show the Abp{tables}. Note that I have already created a navigation from this table to existing App{tables}, so this navigation to the Identity User is the second navigation.

I did test this using a very simple project and it worked.

1. Create a project
2. Added a table: TestTable
3. Created the navigation to the Users/IdentityUser

• When creating the navigation the Collection Names lookup displayed the Abp{Tables} and was able to select the Users entity.

4. Suite generation process succeeded

• This is what the navigation properties shows now.
• Note how the Collection Names field disappeared and the Collection Name=Users, like you suggested

Thanks @enisn